Online courses in ASP.NET MVC / Core, jQuery, Angular, and Design Patterns conducted by Bipin Joshi. Read more...
Learn ASP.NET MVC / Core, jQuery, Angular, and Design Patterns through our online training programs. Courses conducted by Bipin Joshi on weekends. Read more details here.

ASP.NET 5 is now ASP.NET Core 1.0

If you are tracking the progress of ASP.NET 5 you are probably aware of the recent announcement regarding the naming changes to ASP.NET 5. Scott Hanselman wrote a blog post that explains these changes. You can read his post here.

To summarize the changes :

  • .NET Core 5 is now .NET Core 1.0
  • ASP.NET 5 is now ASP.NET Core 1.0
  • ASP.NET MVC 6 is now ASP.NET Core MVC 1.0
  • Entity Framework 7 is now Entity Framework Core 1.0

This article aims at familiarizing you with these changes so that you can get an idea as to what's coming up next.

Web Application build with ASP.NET Core 1.0

Have a look at the following figure that shows how a typical ASP.NET Core 1.0 web application will look like:

The topmost layer is your web application that is built using ASP.NET Core 1.0. Assuming that this application is a typical data driven application, you will use :

  • ASP.NET Core MVC 1.0 to develop that application's user interface and program flow (Model - View - Controller concepts remain the same as in case of MVC 5.x).
  • Entity Framework Core 1.0 (EF Core 1.0) for database programming.

The web application built using ASP.NET Core 1.0 can target .NET Framework 4.6 and / or .NET Core. The .NET Framework 4.6 runs on top of some flavor of Windows operating system such as Windows 7 / 8 / 8.1 / 10. On the other hand .NET Core 1.0 is a cross platform framework and runs on top of Windows and Non-windows operating systems. The .NET Core 1.0 doesn't include all the features and functionality of .NET Framework 4.6 (as of this writing).

Impact on the code written using RC1

You might have developed some projects using RC1 of ASP.NET 5, MVC 6 and Entity Framework 7. Although it's not crystal clear at this point in time as to how much rework you will need to do to get older code working on the new frameworks, here are some clues :

  • NuGet packages, assemblies and namespaces with current names of the form Microsoft.AspNet.* will change to Microsoft.AspNetCore.*
  • NuGet packages, assemblies and namespaces with current names of the form EntityFramework.* will change to Microsoft.EntityFrameworkCore.*
  • The version numbers of all the above NuGet packages and assemblies will be reset to 1.0

Ok. That's it for now! Keep coding!!




Bipin Joshi is a software consultant, trainer, author and a yogi having 21+ years of experience in software development. He conducts online courses in ASP.NET MVC / Core, jQuery, AngularJS, and Design Patterns. He is a published author and has authored or co-authored books for Apress and Wrox press. Having embraced Yoga way of life he also teaches Ajapa Meditation to interested individuals. To know more about him click here.

Get connected : Twitter  Facebook  Google+  LinkedIn

Posted On : 25 Jan 2016



Tags : ASP.NET Data Access MVC C# Visual Studio