IT:AD:ASP.NET:Core:HowTo:Choose Between ASP.NET 4 and ASP.NET Core
Summary
The advantages of choosing the next version of a Framework include: * Longer supported lifespan * Less bugs in core functionality * More features * More reliance on Convention over Convention (as framworks evolve, common Conventions become apparent, and backed into the Framework).
But choosing the next version is not the same as jumping on a totally different product, rebuilt from the ground up – which is what ASP NET Core is.
At present (Q3/2017), stay away from using it for production work due to the following constraints: * Does not have OData sorted out. Which is a big deal: no current app should go out the door without being an API-First, Open Data application in order to allow for SPA clients as well as connections from other systems. And it's simply cost ineffective without making the Controller an OData capable one. * EF Core is coming along, and I think it's just about sufficient…but I'd worry about edge cases. Even MS are currently saying it's not really Prod Ready. * ASP.NET Core is going to continue moving towards being supported only on .NET Core. After the last uproar (see resource links below) they did back off cutting support of .NET Framework, but only for a while. And that will mean a lot of libraries have to be made available first. * As far as I can tell, Microsoft is in a bit of jam on their long term strategy of not squandering their current .NET Developer Community, while opening up to development on Linux and iOS. .NET Standard will eventuate – providing Access to most of .NET 461 from ASP.NET Core – but not sure 'when'.
- Reminder: even the underlying framework issues get sorted out, OData support needs to available before moving onto it.