So, .NET Core, the Great New Framework. I've been playing with it for a while now, and it works fine. I like the api designs and the new ways to configure stuff.

​

That said, at my office it seems unlikely that we'll start using it anytime soon. We've been building on .NET Framework for years and most sites that we're managing are running on a huge set of internal libraries and tools which are heavily intertwinted with System.Web and other aspects of what suddenly became The Old Way Of Doing Things in ASP.NET. Rebuilding all this for Core is a huge task, and no customer of ours is going to pay us to do something like this.

​

So, in practice there's no real reason for us to migrate. Sure, Core seems to perform better but most of our websites don't have a lot of users or traffic since they're private websites for other companies, so performance usually is a non-issue. And other than that, I can't make any real argument for why we should switch, other than 'it's new and shiny'. Especially since .NET Framework isn't going to go away anytime soon. Even for new projects, the cost of having to do a lot of stuff from scratch because we can't use existing libraries and tooling is pretty high. Combined with the fact that my boss is rather conservative in terms of 'new stuff', I doubt that we're going to use .NET Core until there's some reason that we're forced to.

​

Does anyone recognise this problem and mindset? How is your company handling it?