The problem would be a non-privileged user gets updated to my new WebView2-based version of my app and then runs it, it could fail due to lack of WebView2 runtime, and then that user cannot install WebView2 runtime if needed. Unfortunately, the currently available Webview2 Runtime installer requires elevated privileges to install and that is a problem since Windows Store apps do not install/run with elevated privileges.
If necessary, I need to be able to install/update the WebView2 Runtime at runtime from my application. The Microsoft Store does not provide WebView2 package support (and likely do not intend to), so my application will need to check for WebView2 when it runs, (1) whether it is there at all, and (2) what version. I have redeveloped the app to replace CEF with WebView2. \win-arm64\native\WebView2Loader.I develop a Microsoft Store application that currently deploys with CEF. These are SDK files that must be included in addition to the Fixed Version WebView2 Runtime files described above. Make sure you are also installing the WebView2 assemblies and loader files as described on Files to Ship With the App. The error about Web does not exist in Microsoft sounds like a missing reference to the WebView2 nuget package. If you are using something to build an installer, it should let you reference the folder of the Fixed Version files to have placed in the install path of your application. If Fixed Version makes the most sense for your application, you need to ensure that all of the files in the cab package are on the disk somewhere for your app to reference them. You can read more about the pros and cons of both approaches. It will save disk space on the end user's machine since its shared with other apps using evergreen WebView2 and its automatically kept up to date for you, unlike Fixed Version. Generally we recommend using the Evergreen distribution model.
0 kommentar(er)
