Also if your stack is .NET you definitely need Windows Server. Even Amazon has some things built on .NET/Windows Server (woot.com)
I am running it in ubuntu production environment for an App i made. Very stable.
It should absolutely be done, any company with old .net framework solutions that are not actively looking at moving them to .net core is being foolish.
But lots of companies are foolish.
If it only were that easy to move to Core. I thought I could sneak that transition into a few projects but there are a ton of little obstacles that make such an effort lots of work.
The fact that you can target .net standard with framework means TODAY you can sequester your framework specific things behind DLL's and put everything else on .net core officially.
I honestly think there's going to be a huge consulting/freelance market for it soon.
I wasn't trying to imply that it's easy, just that everyone should be planning out how to do it so they can do it slowly over the next few years rather than all at once in panic mode.
Props to MS for ensuring the two can live side by side the way they have. It makes the transition a LOT easier if you're smart enough to start it early and let it have a long tail.
I've personally done this a few times already.
The .net core project indeed runs fine on Linux in AWS. It's a great success story for us.
The ASP .NET projects I maintain have a budget that doesn't easily allow us to just migrate them to .net core. There are some hairy legacy libs and code in there that would also prove challenging to resolve too.
There's also the question of SQL server. It's not so much of an issue when you're dealing with Azure, but SQL server on Linux isn't ready for prime time yet IMO.
-ish, from what I've heard of colleagues struggling with it.
Advanced features like the SQL agent and SSIS/SSAS/SSRS came later but the latest edition has pretty much reached parity across Windows and Linux.