People, this is 2016. If you’re waiting on your project to build or feel like your IDE is sluggish, it’s time to inventory and make sure you have the optimal configuraiton for development rig. Let’s talk quickly about the things that make your machine go fast (or slow) and some simple tweaks that can get your builds moving along more quickly.
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.