When the WebView2.Runtime package is added to WinUI a project, then the following dependencies are added to the project's publish output appx package:
<PackageDependency Name="Microsoft.VCLibs.140.00" MinVersion="14.0.33519.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/>
<PackageDependency Name="Microsoft.VCLibs.140.00.UWPDesktop" MinVersion="14.0.33728.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/>
We intended to add WebView2 Runtime to allow a self-contained deployment without any dependencies. Now we get two new dependencies added, which we would need to manually install on target machines. Newer Windows builds happen to include them already, but older ones (e.g. 22H2) do not have them and need manual installation.
Are these really needed? WinUI 3 does not need them anymore due to Hybrid CRT. They are still added by default, but they are unnecessary and can be removed by a property switch. Can you check if they are really still needed for WebView2? Maybe they can be removed here as well?
When the WebView2.Runtime package is added to WinUI a project, then the following dependencies are added to the project's publish output appx package:
We intended to add WebView2 Runtime to allow a self-contained deployment without any dependencies. Now we get two new dependencies added, which we would need to manually install on target machines. Newer Windows builds happen to include them already, but older ones (e.g. 22H2) do not have them and need manual installation.
Are these really needed? WinUI 3 does not need them anymore due to Hybrid CRT. They are still added by default, but they are unnecessary and can be removed by a property switch. Can you check if they are really still needed for WebView2? Maybe they can be removed here as well?