This is referred to as implicit initialization. 2) Set the Source property (which could be done from markup, for example). This is referred to as explicit initialization. There are two ways to cause the CoreWebView2 to be created: 1) Call the EnsureCoreWebView2Async method. This is because creating the CoreWebView2 is an expensive operation which involves things like launching Edge browser processes. Upon creation, the control's CoreWebView2 property will be null.
On the first/main Form1 window, click NavigateĪlso I noticed that you have the following Thanks again! BTW, it seems that we can implicitly initialize the CoreWebView2 just by setting the Source property.Run the program: Debug => Start Debugging.Uncomment e.NewWindow = ((Form1)s).webView2.CoreWebView2 in CoreWebView2_NewWindowRequested.You'll also notice that the text (html) no longer exists on the first/main form after "Open Popup Window" is clicked. Remaining issue: If the following line of code e.NewWindow = ((Form1)s).webView2.CoreWebView2 is uncommented, you'll see the error message: "The group or resource is not in the correct state to perform the requested operation." after "Open Popup Window" is clicked. You'll notice that I've commented out e.NewWindow = ((Form1)s).webView2.CoreWebView2 in CoreWebView2_NewWindowRequested. You didn't go into much detail about what you're trying to accomplish, so the modified code is only slightly modified and may not perform as desired. You need to initialize CoreWebView2 before using it by calling "EnsureCoreWebView2Async" as specified in Getting started with WebView2 in Windows Forms apps (Preview). One error I noticed was "The group or resource is not in the correct state to perform the requested operation. You didn't specify what error you received.
0 kommentar(er)
