There are some new ASP.NET Core project templates released to play with. Using these templates you can create a MVC starter application, a static website application template and Vue.js with WebPack. At this point of time, it’s not clear whether they are going to be part of official ASP.NET Core templates. To use them, you need to download a VSIX extension (more…)
Prior versions of ASP.NET Core 1.0, have custom errors for error handling. With ASP.NET Core 1.0 and MVC, you can do the error handling via Middlwares. HTTP 404 is a very common error which comes when server can’t find the requested resource. In this post, we will see different ways to handle HTTP 404 error in ASP.NET Core 1.0 and MVC.
Tag helpers are one of the new features in ASP.NET Core MVC 1.0 and previously I posted about how to use select tag helper in ASP.NET MVC Core 1.0. Image tag helper is an alternative for
Html.Image. And in this post, we will see how to use image tag helper in ASP.NET Core MVC 1.0.
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.
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.