IT:AD:ASP.NET:Core:HowTo:Choose Between ASP.NET 4 and ASP.NET Core [Notes]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
# IT:AD:ASP.NET:Core:HowTo:Choose Between ASP.NET 4 and ASP.NET Core #

<callout type="Navigation" class="small">

* [[../|(UP)]]
{{indexmenu>.#2|nsort tsort}}
* See:
  * [[IT/AD/ASP.NET/Core/HowTo/Configure/New App/]]
  * [[IT/AD/ASP.NET/WebAPI/HowTo/Configure/New App/]]


</callout>


<panel title="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 [[IT/AD/ASP.NET/Core/|ASP NET Core]] is.

<callout icon="true" type="important">
I'm a firm believer in using the most spanking new technology. Except in this case at this point in time (Q3/2017).

At present (Q3/2017), stay away from using it for production work due to the following constraints:
* Does not have [[IT/AD/OData/|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 [[IT/AD/SPA/|SPA]] clients as well as connections from other systems. And it's simply cost ineffective without making the Controller an [[IT/AD/OData/|OData]] capable one.
* [[IT/AD/EF Core/|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.
* [[IT/AD/ASP.NET/Core/|ASP.NET Core]] is going to continue moving towards being supported only on [[IT/AD/.NET Core/|.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, [[IT/AD/OData/|OData]] support needs to available before moving onto it.



</callout>


</panel>


## Resources ##
* https://github.com/aspnet/home/issues/2022
* https://www.theregister.co.uk/2017/05/11/microsoft_asp_net_core_2_0/
* https://www.infoq.com/news/2017/05/ASPNET-Core-2