When embedding a web page in your Windows desktop or mobile application usually one requires to have some kind of communication between them.
In the old Internet Explorer days, the WebBrowser component was the way to go and a web page could send a message by writing it on the status bar. The application would then read the status bar content and this simple mechanism allowed some kind of communication.
These days Internet Explorer and the status bar are pretty much dead and there are different ways to communicate.
The WebView2 is the current way to go (get it from NuGet) and even it it is a far more complete and complex component, upgrade is not really that hard for the basic stuff such as getting the event of document complete or location has changed.
WebView embraces new ways for interoperability between the application and the web page.
One simple way to replace the status bar messages mechanism is to use the ExecuteScriptAsync to execute JavaScript code to read information from your page. For instance, using the old hidden field trick as a message store.
But new and more powerful ways are available to have better communication.
While researching on this topic, I found a post that describes multiple ways to reach this goal, like using "postMessage" and "hostObject": Chromium WebView2 Control and .NET to JavaScript Interop - Part 2
Microsoft also has tutorials on this:
- Get started with WebView2 in WinForms apps (check Step 10 if you know the basics)
- Interop of native-side and web-side code
./M6
Posts
