When you distribute your WebView2 app, you need to take into account how the WebView2 Runtime is distributed to and updated on client machines. The download isįor more information, see the WebView2 documentation.When releasing an app that uses Microsoft Edge WebView2, you need distribute the WebView2 Runtime, either by distributing the automatically updated Evergreen Runtime, or by distributing a Fixed Version of the Runtime.Ī WebView2 app depends on the WebView2 Runtime on client machines. Administrators can use their own internal procedures toĭownload and distribute Microsoft Edge WebView2 Runtime to Smart View users. Once installed, Microsoft distributes WebView2 updates on a regular cadence, unless aįixed version was installed. WebView2 versions 86.0.616.0 and later are supported. Microsoft Edge WebView2 Runtime, Oracle recommends using the Evergreen version.

Organization, then you should ensure that Microsoft Edge WebView2 Runtime is installedĪnd enabled on the machines running Smart View.

WebView2 can also be enabled byĮditing the Smart View properties.xml file (by default inĪdministrators: If WebView2 is required to handle the login sequence used by your Section of Health Check (described in Performing a Health Check On Your System in the Oracle Smart View for Office User's Guide). Microsoft Edge WebView2 Runtime installed on the machine and launches the WebView2-basedĬlient machines, users can enable it in the Smart View Options During runtime, Smart View detects the presence of Starting with the 21.100 release, Smart View supports WebView2.

Use WebView2, Microsoft Edge WebView2 Runtime should be installed and enabled on each May require newer controls, such as WebView2, to process a complex login sequence. Oracle Smart View for Office uses the Microsoft InternetĮxplorer module to display the authentication page.

Edge webview2