-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System.TypeLoadException: System.Runtime.InteropServices.IDynamicInterfaceCastable #151
Comments
It sounds like you may have a .NET 6 image. Does this work in .NET Framework on Windows? |
This is the official Minecraft installer for Windows 10, it's probably dotnet 6 as I had to copy some dlls to make it works.
( Minecraft installer for Windows 10 and Minecraft installer for Windows are completely different )
I added The logs of my wine install with Microsoft dotnet and all needed dlls says:
|
I'm really more interested making a simple stub before doing anything else, the goal of this issue is not to make the Windows 10 installer of Minecraft works on wine, just to make progress on app compatibility on wine. As I said, I'm more interesting in contributing to wine-mono than making Windows 10 launcher installer works (Minecraft Bedrock edition requires the Windows 10 launcher) So if I just had a better idea of where to contribute this code this would be enough for me to make a basic stub for |
My Windows machine does not have those dll's, so I suspect what we actually need are winmd files. These would be out of scope of Wine Mono and should be part of Wine, probably generated from its existing WinRT idl's. Supporting winmd files is in scope and likely to be a large project that touches things at a low level. |
I'm also unsure that implementing IDynamicInterfaceCastable is the right thing, since according to MSDN that type is not supported by .NET Framework. |
I agree that But |
MSDN says it's in .NET 5, not Framework. |
This is dotnet5+ related, closing according to #15 (comment) |
Mono logs:
I was a bit confused of where I should contribute, so I decided to open an issue here instead.
upstream mono seems the best, but the the last time I contributed to upstream mono I just found out it didn't affected wine-mono due to using another source for it's wpf implementation. (See #121 for reference)
The text was updated successfully, but these errors were encountered: