Liang Zhao - MSFT

The behavior depends on how .NET implements with IDispatch witch WebView2 uses to interact with host objects. Which version of .NET are you using? In my project targeting .NET Framework...

It is the known issue with .NET core interaction. The issue repros with .NET core but not legacy .NET Framework. No easy fix from WebView2 side. The hit of TestMethodB...

Figured out why it didn't repro for me with .NET Framework and repro for you. I also have `[ClassInterface(ClassInterfaceType.AutoDual)]` on the class. If you add that to the class, it...

It seems that the .NET's type info for the IDispatch doesn't contain the async methods in its member list. We do use some helper that tries to use .NET reflection...

It is a bug in WebView2. An internal work item has been created and the issue is being worked on. Will update this when the fix is ready. The fix...

The fix has been checked in. It may take a while to be released. It should be in newer WebView2 SDK with version > 1.0.2562.0. We also made a change...

It seems that WebView2 implementation only covers DISP_E_MEMBERNOTFOUND and missed handling of DISP_E_UNKNOWNNAME. Created internal work item to track the issue.

The fix has been checked in and will be available in newer Edge builds with version >= 126.0.2562.0.

Could you please capture net log if it repro again following instructions at [Capture Network Logs (NetLog) from Edge and Chrome (and Electron and WebView2) – text/plain (textslashplain.com)](https://textslashplain.com/2020/01/17/capture-network-logs-from-edge-and-chrome/)?

The netlog doesn't provide any clues. As WebView2 initialization also becomes slow, it seems that something else is going on. Could you please capture an ETW trace (https://github.com/MicrosoftEdge/WebView2Feedback/blob/main/diagnostics/etw.md) and share...