ASP.NET's New Versioning Gets To the Core of the Matter

ASP.NET 5.0 is no more, at least by name -- it's now ASP.NET Core 1.0. Newer versions of .NET Core 5 and Entity Framework 7 will also follow suit.

ASP.NET 5.0 is no more, at least from a naming standpoint. With a thorough revamp of its internals, it's being called ASP.NET Core 1.0. And so are newer versions of .NET Core 5.0 and Entity Framework 7, which in their final released versions will be called .NET Core 1.0 and Entity Framework Core 1.0, respectively.

"Why 1.0? Because these are new. The whole .NET Core concept is new," writes Microsoft's Scott Hanselman, in his eponymously named blog. As such, Hanselman emphasizes the 1.0-ness of these versions, and like 1.0 versions these releases are early in development.

"To be clear, ASP.NET 4.6 is the more mature platform. It's battle-tested and released and available today," he writes. "ASP.NET Core 1.0 is a 1.0 release that includes Web API and MVC but doesn't yet have SignalR or Web Pages. It doesn't yet support VB or F#. It will have these subsystems some day but not today."

Early comments on the name change appear favorable. "Good choice. I was struggling with trying to explain ASP.NET 4.6 vs 5 with my developers and that it wasn't the same as 3 to 4. This makes it clear," writes commenter Bill Simser.

Another comment, from Damien Dennehy, came with a question:

This is cool and makes total sense, but for class library owners what's the impact (if any) to framework monikers? A year ago you needed to target dnxcore50 for ASP.NET Core 1.0. Currently it's dotnet, and this is going to change soon to netstandard. Is this going to change again now?

Hanselman's reply was simple: "'netstandard' is the way forward, Damien."

About the Author

You Tell 'Em, Readers: If you've read this far, know that Michael Domingo, Visual Studio Magazine Editor in Chief, is here to serve you, dear readers, and wants to get you the information you so richly deserve. What news, content, topics, issues do you want to see covered in Visual Studio Magazine? He's listening at [email protected].

comments powered by Disqus


  • Top 3 Blazor Extensions for Visual Studio Code

    Some developers prefer to create applications with Microsoft's open-source Blazor tooling from within the open-source, cross-platform Visual Studio Code editor. Here are the top tools in the VS Code Marketplace for those folk, as measured by the number of installations.

  • How to Invert a Machine Learning Matrix Using C#

    VSM Senior Technical Editor Dr. James McCaffrey, of Microsoft Research, explains why inverting a matrix -- one of the more common tasks in data science and machine learning -- is difficult and presents code that you can use as-is, or as a starting point for custom matrix inversion scenarios.

  • Microsoft Engineer: 'It's Time to Move OData to .NET 5'

    Microsoft engineer Sam Xu says "it’s time to move OData to .NET 5" and in a new blog post he shows how to do just that.

  • Microsoft Goes Virtual with Developer Education in Face of COVID-19

    Like many organizations that host developer educational events, Microsoft has gone virtual amid shelter-in-place directives and a surge in remote work stemming from the COVID-19 pandemic.

  • Microsoft Enhances Low-Code Power Apps

    Microsoft's nod to the low-code movement, Power Apps, has been enhanced with a bevy of new features, including mixed reality, canvas/model support in a new mobile app, UX improvements and more.

.NET Insight

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.

Upcoming Events