Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Using ASP.NET Core TagHelpers [Podcast]

DZone's Guide to

Using ASP.NET Core TagHelpers [Podcast]

This podcast focuses on implementing ASP.NET Core UIs with a focus on TagHelpers. See how you can put them to use in web development.

· Web Dev Zone
Free Resource

Tips, tricks and tools for creating your own data-driven app, brought to you in partnership with Qlik.

Recently, Microsoft announced the release of ASP.NET Core 2.0. With this release comes a new feature for building HTML views called TagHelpers. With ASP.NET Core 2.0, TagHelpers allow developers to write component based-views for server-side rendering by utilizing a syntax similar to HTML. This new syntax incorporates concepts used in HTML, elements, and attributes.

When using TagHelpers in a .cshtml view, Visual Studio treats the TagHelper as it would HTML, but with added server-side functionality. Often with HTML Helpers, the CSS class attribute was difficult to add and completely lacked Intellisense. With TagHelpers, developers get rich Intellisense for not only server-side code, but also with any HTML attributes supported by Visual Studio.

In addition to better Intellisense, TagHelpers also make great container elements. TagHelpers treat their inner HTML content as normal HTML elements do. In comparison to HTML Helpers, nested content required escape codes, or specialized using blocks to contain inner HTML content.

Throughout .NET’s journey from conceptualizing ASP.NET Core TagHelpers to our recent release, Progress has continued to support the community by sharing information about TagHelpers. Below are resources that will help keep you up to speed on the latest developments with ASP.NET Core TagHelpers.

Explore data-driven apps with less coding and query writing, brought to you in partnership with Qlik.

Topics:
web dev ,taghelpers ,asp.net core ,html views

Published at DZone with permission of Ed Charbeneau, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}