[Blazor] Discourage use of `DotNet.invokeMethod` and `DotNet.invokeMethodAsync`

[MackinnonBuck]

The DotNet.invokeMethod and DotNet.invokeMethodAsync APIs currently throw when more than one interactive runtime is present. We should be encouraging developers to replace usage of these methods with DotNetObjectReference method invocations so that JS->.NET interop works regardless of which combination of .NET runtimes are available.

We should consider logging a warning during development if we detect usage of DotNet.invokeMethod or DotNet.invokeMethodAsync.

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.