Closed masaeedu closed 6 years ago
dnx (+dnvm/dnu) is being retired in RC2 and the new command line experience is through dotnet CLI (https://github.com/dotnet/cli)
@muratg I didn't know that, thanks. Is this a feature that's already available in the new CLI (or planned to be included)?
@masaeedu "runtime" concept is different in the new world, as such you won't need DNVM or similar. Basically for CoreCLR apps will either bring the runtime with them or will use a shared runtime install. For desktop, though all the dependencies are brought in with the app (except those already existing in the full CLR)
@muratg When you say full/shared CLR, I'm assuming this refers to the full Microsoft CLR on Windows and Mono on Linux. However, I'm developing a console application that will run on Linux on my Windows box.
Since code and dependencies that build and run on .NET 4.5 are not guaranteed to run on Mono (e.g. because of differences in the BCL), I need to compile and test against Mono. How would I do this with the new CLI (if this is at all possible)?
@masaeedu Not sure if that's still a scenario in the CLI world. I recommend asking this out there, or in StackOverflow
I want to develop an app that will run on Linux using the mono runtime (the libraries I need aren't CoreCLR ready yet). The development will be done on my Windows box. I tried installing the mono runtime using the following command:
Which resulted in the following error:
So I provided an argument for os:
This seems to work initially, but eventually chokes:
Is this a bug in the DNVM script, or is mono on Windows not supported? If not, would a mono on Windows DNX be a reasonable feature request?