ASP.NET 5 is now ASP.NET Core 1.0

Last week Microsoft announced that ASP.NET 5.0 has been renamed to ASP.NET Core 1.0. And it’s a welcome change and quite needed to address the confusion. As ASP.NET 5 is completely a new platform to build cross platform applications and it was written from scrath. The latest version of ASP.NET is 4.6 and It is possible to run ASP.NET 5 on top of the full .NET 4.6 Framework/platform or to run ASP.NET 5 on .NET Core.

Go ahead and read my post Quick summary of what’s changed in ASP.NET 5 and What’s coming in ASP.NET RC 2 before you go further.

ASP.NET 5 is now ASP.NET CORE 1.0

As also mentioned by Scott in his blog post,

However, naming the new, completely written from scratch ASP.NET framework “ASP.NET 5” was a bad idea for a one major reason: 5 > 4.6 makes it seem like ASP.NET 5 is bigger, better, and replaces ASP.NET 4.6. Not so.

Here are the new names.

• ASP.NET 5 is now ASP.NET Core 1.0.
• .NET Core 5 is now .NET Core 1.0.
• Entity Framework 7 is now Entity Framework Core 1.0 or EF Core 1.0.

Why 1.0? Because these are new. The whole .NET Core concept is new. The .NET Core 1.0 CLI is very new. Not only that, but .NET Core isn’t as complete as the full .NET Framework 4.6.

So now the question is that these are only name change or as a developer do we have to also make any changes? Well, the answer is YES.

The version of libraries and nuget package will change and requires developer attention. So what actually changed, other than name?

What changed?

• The Microsoft.AspNet.* packages and namespaces are changing to Microsoft.AspNetCore.*.
• The EntityFramework.* packages and namespaces are changing to Microsoft.EntityFrameworkCore.*.
• The version numbers of all of the above are being reset to 1.0.0-*.
• MVC 6 is now ASP.NET Core MVC 1.0
• Microsoft.AspNet.Identity.EntityFramework package being renamed to Microsoft.AspNetCore.Identity.EntityFrameworkCore

Conclusion

The decision to rename ASP.NET 5 to ASP.NET Core 1.0 is the right decision and it was required as well. But I believe they are bit late to rename this as this is affecting the nuget packages and libraries. But there is a saying “It’s never too late – in fiction or in life – to revise”.

That’s all folks for now. Keep visiting for updates and share this in your network.

PS: If you found this content valuable and want to return the favour, then