Jan Kotas

> Does this sound like a plausible approach? Hosting both CoreCLR and CoreRT in the same process sounds pretty non-trivial. You may want to take a look at https://github.com/SharpGenTools/SharpGenTools ....

Agree - making SharpGenTools work for Windows Forms/WPF would need some work. Still, I think it is easier to make SharpGenTools work than to make both CoreCLR and CoreRT run...

We have abandoned the MCG tool. We do not have plans to open source the MCG tool anymore. Yes, generating the interop marshaling code using build-time tooling is the way...

Here is how to start on this. 1. Install latest .NET 5 SDK preview from https://github.com/dotnet/installer 2. Create .NET 5 WinForms app 3. Add the following to Program.cs and the...

1. You can create you own fake WinForms.dll to compile the COM wrappers against. E.g. the projects can be structures like this: - MainWinForms app - References real WinForms.dll -...

> On the other hand, there is the option to handle this at the original callsite. Agree that is possible to address all of this by changing the calling code....

> What information do you think would be helpful here? The user provides the desired type in some cases, e.g. `Marshal.GetTypedObjectForIUnknown` that is getting lost now. But I agree that...

I would use WinDbg myself. If you share stacktrace of the crash or link to a branch with the code, we may be able to give you some more tips.

> This is essentially what Android does and it works quite well there. This works when the runtime is part of the OS (or part of large app with complex...

A few angles to consider: - Microsoft official build vs. source build: We can bump the baseline for Microsoft official build, keep the code for x86 v1 around for the...