ReviewCoreASP.NET | Best and cheap ASP.NET MVC Core 1.0 hosting. 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.
[su_note note_color=”#59e0c4″ text_color=”#ffffff”]
ASP.NET MVC 5 vs ASP.NET CORE MVC 1.0
[su_note note_color=”#d9ae89″ text_color=”#0f0d0d”]
ASP.NET CORE MVC 1.0 is Cross Platform.
ASP.NET Core MVC 1.0 is Cloud Ready.
MVC + Web API + Web Pages = ASP.NET Core MVC 1.0
ASP.NET Core MVC 1.0 doesn’t need IIS for hosting.
ASP.NET Core MVC 1.0 has inbuilt support for Dependency Injection.
ASP.NET Core MVC 1.0 has a new project solution structure.
Roslyn compiler for compiling code dynamically.
In ASP.NET Core MVC 1.0 “wwwroot” is now place for static files.
default root of your server. If a request comes in for a static file on disk, if the file is in this folder then it can go back to client. The name can be changed from project.json file.
Everything is Nuget package in Core MVC 1.0. There is no dll by default.
Manage client side dependencies via NPM and Bower.
Introduction of _ViewImports.cshtml in Core MVC 1.0
Introduction of Tag helpers.
It also support RESTful style routes with attribute routing
That means you can even declare RESTful like routes like [HttpGet(“Our Route”)] and [HttpPost(“Our Route”)]
In Core MVC 1.0, routes have new [controller] and [action] tokens.