You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Documentation about the WebView2 Evergreen distribution mode suggests detecting updates to the WebView2 runtime via the NewBrowserVersionAvailable API and using that notification to potentially restart the application to use the new version. However, related to this discussion, I haven't been able to find any way to roll back the installed WebView2 runtime to a previous version. I also tried running an older fixed runtime version using the BrowserExecutableFolder registry key (as documented here), but although that loads the expected runtime, the NewBrowserVersionAvailable event never fires.
Aside from simply waiting for a new WebView2 runtime version to be released, how can we authentically test workflows that aim to test detecting new versions?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Documentation about the WebView2 Evergreen distribution mode suggests detecting updates to the WebView2 runtime via the
NewBrowserVersionAvailableAPI and using that notification to potentially restart the application to use the new version. However, related to this discussion, I haven't been able to find any way to roll back the installed WebView2 runtime to a previous version. I also tried running an older fixed runtime version using theBrowserExecutableFolderregistry key (as documented here), but although that loads the expected runtime, theNewBrowserVersionAvailableevent never fires.Aside from simply waiting for a new WebView2 runtime version to be released, how can we authentically test workflows that aim to test detecting new versions?
Beta Was this translation helpful? Give feedback.
All reactions