4 hours ago
Hi,
Thank you for your question.
That the demo expired is not related to your problem.
The control remains fully functional, but you'll get a nag popup on navigation every now and then.
Your issue is that the NavigateToString method does not automatically send a CreateWebView whereas Navigate does.
Creating the control like you did, only creates the AntView ActiveX wrapper, in order for the WebView2 control to function, it needs to create background WebView2 processes. There are not started automatically when you use NavigateToString.
Sending CreateWebView starts those processes.
The solution to your problem is to send a CreateWebView before the NavigateToString.
Hope this helps,
--
Wil
Thank you for your question.
That the demo expired is not related to your problem.
The control remains fully functional, but you'll get a nag popup on navigation every now and then.
Your issue is that the NavigateToString method does not automatically send a CreateWebView whereas Navigate does.
Creating the control like you did, only creates the AntView ActiveX wrapper, in order for the WebView2 control to function, it needs to create background WebView2 processes. There are not started automatically when you use NavigateToString.
Sending CreateWebView starts those processes.
The solution to your problem is to send a CreateWebView before the NavigateToString.
Hope this helps,
--
Wil