nightcraw1er.488: Yes, the vs2019 is a stub from which you can install many components. .net code sounds like the best option for you. .net cli is not on Mac so you need some sort of layer for that to work. What code is it you want to move across, for more important projects perhaps a good idea to build a pipeline for it. Perhaps a web process or javascript version?
Vs2019 is all you need and would not recommend earlier versions.
Just to clarify, when you say ".net code" do you mean ".net
core"? I'm not trying to nitpick, but just making sure that we're talking about the same thing. And I'm not sure what ".net cli" is. I can't use javascript or other stuff like that for it because it needs to be able to run completely offline.
wpegg: With the caveat that I've never actually tried it on a mac, I think you're basically correct. You just need to download vs2019 (as nightcrawler said, it's just a stub and depending on the features you install, it will in fact download several GB), then make sure you select the .NET core runtime (vs2019 can build 3 different types of .NET, so make sure you select Core, I'm not certain that is the default). All dependencies are copied to your bin directly (they aren't bundled into the exe, but you'll have it all in one folder), then you can xcopy deploy your application, or if you want you can even publish your application so that it has a basic installer (depending on project type).
It's several GB to download? Well the SDK that I got and any other installers are all much less than that. Are you implying that it downloads
during installation? Like I said, I intend to install it on an air-gapped computer, meaning one that is completely disconnected from any network including the Internet. I don't know about all of this xcopy stuff, because I was just going to select the .EXE file and possibly a folder to go with it, and copy it onto a thumb drive for distribution. I don't want an installer because it needs to remain on the thumb drive.
wpegg: It's not identical to .NET, the libraries are different, and the apis can have different interfaces, but it's pretty mature now, so should be good enough for your purposes (depending on what they are, you haven't, to my knowledge, told us what kind of project you're compiling, I think WPF might need the full fat framework still).
I also think there might be a few more hoops to jump through, this article may give some insight:
https://www.michaelcrump.net/part3-aspnetcore/
I still think it's your best bet though.
Well it's not WPF. It's about the most basic, regular, non-ASP or any other alternative thing - just a plain Windows application. And thanks for the link.