Closed adammarks closed 4 years ago
How strange. Two ideas:
dotnet new wpf
in an empty directory, does that app run? If so, what does it's runtimeconfig.json look like?@mjrousos I do get farther with x64, I can run the app but then when I try to hit C++/CLI code I get the following https://www.screencast.com/t/QKdvqOE54wNj
@mjrousos I did a dotnet new wpf
and that works fine, but then when I change the Platform target to x86 I do get the same error https://www.screencast.com/t/9ncwPMmoR
Interesting. Sounds like there may be bitness issues. Can you make sure that you have an x86 version of the .NET SDK installed that corresponds with the version listed in the runtimeconfig.json
file?
@mjrousos I did get past this error for the x86 builds by installing the x86 version of .NET core also.
But, I still get a BadFormatException when I try to load the C++/CLI assembly
I wrote a separate bug for the BadFormatException https://github.com/adammarks/netcoreproto/issues/5
I created a example of a Managed entry point C++/CLI Interop app with .net 4.7.2 , made sure that worked, then converted it to .NET Core 3
The app builds fine as Debug / x86 or Release / x86, but when I run, I get the following error message
This doesn't make sense to me because I have that release installed, here's my .net core info
This is the ManagedInteropApp.runtimeconfig.json 's contents