Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Can't run with Linux/Mono/dotnet-cli #963
Hello David, thanks for replying!
Do you mean that because OS detection is broken at the moment Kestrel tries to load a Windows DLL? That explains it, I guess.
I tried the workaround in #942 however I am still getting the DLL not found exception for
I know Mono isn't supported, but the application I am working on has some libraries which are not yet compatible with .NET Core runtime and that's why I'm still targeting
Thanks for your help.
Yep! The workaround won't work I'm assuming it's picking the windows dll with the
On unsupported mono? Test for what purpose?
No idea, we no longer test on mono.
@davidfowl, when did mono stop being apart of your test matrix? I don't recall seeing an announcement that mono was longer even tested on. There are use cases that .net coreclr doesn't yet support that mono does. Why remove it from the test matrix? Especially given that it was part of the original project announcement that mono was going to be a tested and supported platform.
Tried it, still not working but I am getting a different error: https://gist.github.com/nmilosev/30da19909b83570f8e4e4a59af401cfe
I'm developing on Linux with Visual Studio Code, so it would be nice to be able to run the application without a virtual machine. I also tried Docker, but since it is also Linux (Ubuntu) inside, it does not work.
I'll stick to Windows VM for now, but I hope we will be able to use Mono to test/run full CLR applications on Linux, at least until more libraries are compatible with .NET Core.
Thanks again for your time David!
I made it work.
You have to use latest mono:
I installed it from Fedora Rawhide repository.
Afterwards you have to do the following:
Application runs now, and everything is the same as with RC2, which means that the only thing not working is the date cast I mentioned. :( I think that's Mono related so I will try to see there or with the EF Core team.
Gonna try to fix that.
Thanks David for
referenced this issue
Jul 14, 2016
I was also having this problem on OSX, and when I looked at the debug output of Mono, I noticed that the reason System.Native wasn't being loaded was because Mono claimed it was the wrong architecture. After digging a bit (with an assist from @akoeplinger on slack), this is what I found.
CLI is just exec'ing 'mono'. On my system (El Capitan on a new MacBook Pro), I installed mono via homebrew, and the
P.S. - if mono isn't finding the System.Native library at all, then you can create symlinks (I did), or you can use