Select Developer Command Prompt for Visual Studio 2019Ĭ:\Users\Test> cd %ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\0\bin\Host圆4\圆4Ĭ:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\0\bin\Host圆4\圆4> dumpbin "%ProgramFiles(x86)%\Microsoft\EdgeWebView\Application\89.0.774.45\msedgewebview2.exe" /headers | find /i "machine"Ĩ664 machine (圆4) indicates the msedgewebview2.exe file is 圆4.ġ4C machine (x86) indicates the msedgewebview2.exe file is x86.Option 1: Open a Developer Command Prompt for Visual Studio 2019 window %ProgramFiles(x86)%\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\3\bin\Host圆4\圆4\dumpbin.exe.%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\0\bin\Host圆4\圆4\dumpbin.exe.This can be verified by installing the 圆4 version and then use dumpbin.exe to find the version: If one installs x86 version and then the 圆4 version, the 圆4 version will overwrite the x86 version causing one's WebView2 control to display a white (blank) screen. However, the application hung and it would not display the website (white screen).Īfter further investigation, it appears that the WebView2 Evergreen Standalone Installer installs both 圆4 and x86 versions to %ProgramFiles(x86)%\Microsoft\EdgeWebView\Application. The "Microsoft Edge WebView2" processes seemed to get created (as seen in Task Manager), and calling CoreWebView2Environment.GetAvailableBrowserVersionString() seemed to report the correct version. I noticed that if WebView2 圆4 was installed, but not WebView2 x86, my demo application attempted to use WebView2 圆4. I created a demo application and compiled as Any CPU (Prefer 32-bit). NuGet Package Management: PackageReference Runtime: 89.0.774.45 ( Evergreen Standalone Installer) WebView2 Evergreen Standalone Installer installs both 圆4 and x86 versions to %ProgramFiles(x86)%\Microsoft\EdgeWebView\Application.
0 kommentar(er)
