If you are on .NET, migrate to .NET Core. If you start with .NET, start with .NET Core.
Based on:
- [WayBack] Nick Craver on Twitter: “This is worth repeating: We’re migrating Stack Overflow to .NET Core. **It’s not because of performance**. There are enough major wins without even factoring performance for us to move. Any performance gains are 100% in the bonus category. We’d migrate with a 0% perf improvement.”
- [WayBack] Nick Craver on Twitter: “No clue! Honestly. There are enough wins from us in a .NET Core migration (e.g. maintenance, open source/fixes, SDK projects, running in a container or appliance, etc.) that performance literally isn’t on my list. We know it’s better, but really don’t care by how much.… https://t.co/p5TdJdxeVJ”
–jeroen
Edit: nice comment on [WayBack] If you are on .NET, migrate to .NET Core. If you start with .NET, start with .NET Core. Based on: [WayBack] Nick Craver on Twitter: “This is worth repea… – Jeroen Wiert Pluimers – Google+:
We are porting Continua CI to .net core 2.1, I’ve been working on it for a few months now (along with other things of course), I had to contribute to a few open source projects to help get all our dependencies onto .net core, and for the most part it’s been pretty easy. I did have to change the windows service stuff, and since there is no WCF server stuff in .net core we have to find a replacement for that for server to agent communications (still exploring options, but probably going with halibut).What hasn’t (and still isn’t) easy is porting MVC4/5 stuff to asp.net core. So many little changes that drive me absolutely potty. I was getting so frustrated that I had to put it aside for a while and work on other things, just to get my sanity back!