![]() ![]() UWP uses isolated registry access, so it doesn't seem to be able to find the UWP entries when the application is installed in per-user mode. It only seems to work when the WebView2 runtime is installed "global" (not per-user, but per-machine).Only tested within the scope of my application, so no promises. ![]() Developer tools are disabled, because they don't work within UWP programs (it requires creating an external window and that doesn't seem to be supported).Cookies are saved by Edge and are application-scoped.The ExportRenderer automatically wires the WebView2 to the existing Xamarin Form WebView control, so it should be a drop-in replacement. The add the UwpChromiumWebViewRenderer.cs file to your project (code below). I used v2.8.0, but there may be newer versions. Make sure to reference the Microsoft.UI.Xaml package from the UWP project-file. I have implemented a Custom Renderer that implements the Xamarin Forms WebView control and wires everything to WebView2 instead the Edge-based WebView. ![]()
0 Comments
Leave a Reply. |