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.

Be sure to follow the Monsters on Twitter and check out the blog for related posts.

The production code for this video is VG.

Your first impression of configuration in ASP.NET Core may be that a tyrant of a coyote with ACME corporate sponsorship laid into the system with a box of explosives. You wouldn’t be wrong, but here’s why it was the right thing to do.

Your first impression of configuration in ASP.NET Core may be that a tyrant of a coyote with ACME corporate sponsorship laid into the system with a box of explosives. You wouldn’t be wrong, but here’s why it was the right thing to do.

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.

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.

Here comes Episode 3 of The Monsters Weekly, and with it our run down of the default Gulp file in your ASP.NET Core application. Monster Dave walks us through Gulp, some node bits, package management, and how to sort all this out in our new ecosystem.

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.

Over the last two posts I worked through the basics of configuration in ASP.NET and how to leverage structured data in your JSON config files. Now it’s time to take a deeper look at how to access relevant parts of your configuration throughout the rest of your project.

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.