The best way to learn new technologies is via comparing with the old and find out what has changed. In this post, find out the difference between ASP.NET MVC 5 and ASP.NET MVC Core 1.0 aka ASP.NET MVC 6. The difference list is quite long as ASP.NET Core 1.0 is re-written. The basic of MVC still remains the same and we can say that from coding perspective there aren’t many changes but there are framework level changes, project structure changes, hosting and deployment changes and many more. So let’s dive in.
If you are following the progress of ASP.NET Core 1.0, then you must have realized the list of new features of ASP.NET Core 1.0 is quite long. I tried to cover some of them in my earlier posts here and here. And one of the new feature was introduction of a new Class library (Package) project template. This new project template allows you to create Nuget package of your class library, instead of DLL.
Earlier I posted about ASP.NET 5 was renamed to ASP.NET Core 1.0 and with this name change, ASP.NET MVC 6 is now ASP.NET Core MVC 1.0. As ASP.NET Core 1.0 is completely re-written (to make it faster, better, modular and platform agnostic), it has also brought lots of freshness in ASP.NET Core MVC 1.0. The fundamental concepts of MVC remain the same, many of the underlying layers of the framework have changed. So here is quick and short summary of what’s changed in ASP.NET Core MVC 1.0 compared to all its previous versions.
Yes, you read it right “DotNet 5.4“. Create a nuget class library using Visual Studio 2015 and RC 1 update. And take a look at the Project.json file, you will be surprised to see “DotNet 5.4” in the framework section. Recently ASP.NET 5 was renamed to ASP.NET Core 1.0, then from where DotNet 5.4 came from? They are yet to release RC 2 for ASP.NET Core 1.0 and I was like “Have I really missed the release of Dotnet 5.1 to 5.3? “.