ASP.NET Core Tag Helpers

Course Overview
Hi everyone. My name is Peter Kellner, and welcome to my course, ASP. NET Core Tag Helpers. I'm a software engineer at the consulting company, 73rd Street Associates. Tag helpers are far and away the best new feature in ASP. NET Core. Razor view pages now look like clean HTML. This course is laser-focused on tag helpers. Some of the major topics we will cover include authoring our own tag helpers, using the tag helpers the ASP. NET team built for us, building our own JavaScript Manager, and using advanced tag helper features including dependency injection. By the end of this course, you'll know not only how to build your own tag helpers, but you'll be able to use and extend the built-in ones with the advanced knowledge of how they work. Before beginning the course, you should be familiar with ASP. NET MVC. You won't need to know anything about ASP. NET Core, as I will explain the differences Core brings to us. I hope you'll join me on this journey to learn ASP. NET Core Tag Helpers at Pluralsight.

Authoring Your Own Tag Helpers
Hi, this is Peter Kellner, and this module is all about authoring tag helpers in ASP. NET Core. In the last module, we authored a very simple tag helper named my-customer. All it really did was take a single attribute, name, did a hard-coded lookup, and based on that name, output an address. The idea was to give you an idea of what's happening on the C# code side of a tag helper. The tag helper coding model is very simple. The Razor view engine looks for valid tag helpers it knows about on the Razor view page. When it finds one, it calls its Process method; that's it. The design is amazingly simple, however, that simple design gives us a huge amount of power for what we can do. In this module, we will dive into the details of implementing real-world tag helpers, and all the intricacies that brings with it. On a side note, all demonstrations that include Visual Studio are using the 2015 version and include pre-release tooling to support tag helpers. This tag helper tooling is now only available in the now-released Visual Studio 2017, which means that for you to follow along in code you will need to have the latest version of Visual Studio 2017 installed. All our course downloads are setup for Visual Studio 2017. The tag helper API did not change, just the Visual Studio tooling.

Leveraging Built-in Tag Helpers
Hi, this is Peter Kellner, and this module is about the TagHelpers built into ASP. NET Core. Thankfully, not only did the ASP. NET team create the TagHelper architecture, but they also provided us with a set of professionally-built TagHelpers to help us build awesome Razor view pages, that is our cshtml view pages. These TagHelpers provide functionality for us that include enhancing our productivity when building forms, optionally including different HTML in our web pages based on environmental variables such as production or development, caching different parts of our web pages, and much more. In this module, we will learn how to use non-form-based built-in TagHelpers, and while we review them I'll provide insight into when and how to use the built-in TagHelpers to get the biggest advantage for you. On a side note, all demonstrations that include Visual Studio are using the 2015 version and include pre-release tooling to support TagHelpers. This TagHelper tooling is now only available in the now-released Visual Studio 2017, which means that for you to follow along in code you will need to have the latest version of Visual Studio 2017 installed. All our course downloads are set up for Visual Studio 2017. The TagHelper API did not change, just the Visual Studio tooling.

Authoring an Advanced Tag Helper
Hi, this is Peter Kellner, and in this module we will build TagHelpers that use many of the popular features TagHelpers are known for. More specifically, we're going to create a script manager service that works seamlessly with a new BodyTagHelper, as well as a new ScriptTagHelper. So why do we need a script manager? Well, you're probably thinking we already have tons of script managers, why do we need another one? Well, the reason is that we don't have a script manager that integrates with TagHelpers that themselves require JavaScript. Watch and learn what I mean by that. I realize what I just said is a bit vague, but if you follow along over the next couple of sections, it will become 100% clear why we need such a script manager. On a side note, all demonstrations that include Visual Studio are using the 2015 version and include pre-release tooling to support TagHelpers. This TagHelper tooling is now only available in the now-released Visual Studio 2017, which means that for you to follow along in code you will need to have the latest version of Visual Studio 2017 installed. All our course downloads are set up for Visual Studio 2017. The TagHelper API did not change, just the Visual Studio tooling.