One of the many areas which has been revamped completely with ASP.NET 5 is the localization infrastructure. Anže Vodovnik takes a look at how you localize Razor views in ASP.NET 5 and MVC 6.
ASP.NET MVC 6 comes with a basic dependency injection container that will allow you to implement constructor and property dependency injection into your controller classes. This may be enough for smaller ASP.NET MVC 6 applications while other applications can continue to use Autofac, Ninject, StructureMap, Unity, etc.
ASP.NET MVC 6 is a ground up rewrite of the popular .NET web platform. Sweeping changes were made throughout, with even some of the most basic elements being reorganized. These changes are immediately apparent when starting a new MVC6 project, especially to developers familiar with previous versions of the framework.
This post is about tag helpers, another feature new to ASP.NET MVC 6. Let's take a look at what tag helpers have to offer.
This article shows how to document your MVC 6 API using Swagger with Swashbuckle. Per default, it does not use your xml comments in the code and this needs to be configured if required.
Child Actions do not exist in MVC 6. Instead, we are encouraged to use the new View Component feature to support this use case. Conceptually, view components are a lot like child actions but they are a lighter weight and no longer involve the lifecycle and pipeline related to a controller.
ASP.NET Core opens the doors to new opportunities for ASP.NET developers through integration points in Bower, NPM, and Gulp. One perk of using common web development tools is that frameworks like Foundation can be installed directly from the vendor whereas before developers needed to rely on NuGet packages.
ASP.NET Core 1.0 is a complete rewrite of ASP.NET, and one of the main goals for this new framework is a more modular design. That is, apps should be able to leverage only those parts of the framework they need, with the framework providing dependencies as they’re requested.