I'm assuming I would just make this check before calling GlobalWebView2Loader. The way I currently detect the presence/version of the WebView2 Runtime is to read the registry. The next thing on my plate will be to figure out the best way to detect, then install/update, the WebView2 Runtime at runtime in my application. Based on the announcement, it is supposed to be available around mid-December (any day now). Microsoft will be updating their Webview2 runtime installer to be able to install the WebView2 runtime without requiring elevation. 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. I develop a Microsoft Store application that currently deploys with CEF.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |