The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
basically i agree since I already can run .NET PEs on linux.
still, i build in .NET core because i'm not sure how deep that compatibility runs - for example, will only linux run a .NET win PE, or will anything running mono be able to? what about the other CLR/CLI implementations, etc? these are all questions I don't currently know the answer to and there are plenty more too. And I don't want to have to find out the answers. So I build in core
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
As long as you don't have a UI, your ,net *framework* app should run on linux/mono. Keep in mind that mono (last time I checked) was SEVERELY behind the power curve as far as .net versions are concerned. If your app DOES have a UI, you may be able tio run it under Wine, but I see that as at least as much of a crap shoot as using mono.
As an alternative, you might want to try writing your code in C++.Net, get it working there, and then ciopying the source code (the cpp files) to a Linux C++ project, and try compiling it native on linux.
I've generally found that as we progress in dev technology, we get further away from being able to do cross-platform dev. This has been a problem ever since Windows was first introduced.
The 'cost saving' action of getting rid of the IT dept has crippled the Kaspersy updates coming over the network. Yes someone took their eye off the ball and didn't update the licence, they now have but can't push it from the server. Before we upgraded to proper IT support we never had this. (Three guys in a HOT room full of PC's and it rarely went wrong, and install codes and manuals could be found in minutes)