Closed JaiganeshKumaran closed 3 years ago
Please fix this, workarounds are hard and not ideal
@Jaiganeshkumaran Are you saying the error message is incorrect?
Or is the "workaround" what it takes to have the C++ reference be compatible?
@orcmid Earlier you can create a C# managed Windows Runtime component and directly reference it from C++ and it will work but now it crashes due to some .NET Core version issue. Some workarounds like modifying the project file for C++ can work sometimes but it's not ideal.
@Jaiganeshkumaran. Could you please provide more info? Do you have a repro case you can share? Which versions of C++ and .NET? Etc.
@Jaiganeshkumaran I've written about this: https://github.com/asklar/WinRTComponent/blob/master/README.md See also Raymond's post: https://devblogs.microsoft.com/oldnewthing/20200615-00/?p=103868/
@asklar I can't do this workaround every time I create a new project also I'm not that familiar with these project files and it's not a good experience. The SDK should ship proper templates in my opinion that doesn't require workarounds.
Agree that it's not a good experience. This isn't a Windows SDK issue though but a .net native issue, so I suggest you should file a bug against visual studio in the developer community site about it (In VS, go to Help, send feedback)
This issue is out of scope for this repository. Per @asklar's response, please file the bug against VS!
If you create a C# component and use it from C++, it will crash at runtime on 1709+.
FUSION_E_REF_DEF_MISMATCH 0x80131040 The located assembly's manifest definition does not match the assembly reference