Well, here we go! This is the inaugural installment of The Monsters Weekly, where we take you up, down through and over all the aspects of ASP.NET Core and Core MVC. In our first episode, we’re covering the startup.cs class and what happens as our application loads.
Not sure where to start in ASP.NET Core? Well, in startup.cs, of course. We run the file top-to-bottom covering some basic configuration, dependency injection, browser link, database error pages, service configuration and the Julie Lerman of Canada. This is an intro - we cover a lot of ground at 30,000 feet, but don’t worry, we’ll be breaking it down in the weeks ahead.
The production code for this video is VG.
Ready for a great new feature in ASP.NET Core MVC? The Razor view engine now supports a concept called “Tag Helpers” that dramatically reduces the “c-sharp-iness” of your view and gives you something that looks a lot more like HTML. Dave, that Monster, constrasts this to the earlier incarnation known as HTML Helpers.
In this, Episode 2 of The Monsters Weekly, we take a deeper look at some of the configuration options and, in particular, how things have changed in terms of serving up static files in ASP.NET Core. We’ll show you how to enable it, how it works in the default template and what you need to do to get it running from a blank canvas.
Feature folders provide an alternative, and possibly better approach to arranging your code inside of an MVC project.
Structured data in earlier versions of ASP.NET meant creating and registering custom types and configuration sections for our applications. In ASP.NET Core and in Core MVC, structured configuration is a breeze with support for JSON documents as the storage mechanism and the ability to flatten hierarchies into highly portable keys.
Did you hear the news? ASP.NET 5 is dead it is now called ASP.NET Core 1.0. The name for this next generation of ASP.net(that’s the capitalization I’m using because this isn’t your grandmother typing in YAHOO.COM) has been up in the air for a while. We first heard the real details about ASP.net vNext at the MVP summit in 2014 and the first question on everybody’s mind was “what it was going to be called?”. At the time there wasn’t a decision on that.