Gain insights into creating dynamic web apps with ASP.NET Core MVC. Explore Razor, localization, advanced features, and best practices for building public and business applications.

ASP.NET Core MVC (Intermediate)_468 x 60 copy.png

asp.tar.gz

ASP.NET

ASP.NET-multi

ASP.NET-Secure

ASP.NET-copy

In this course, you will learn how to create a modular, dynamic web application with ASP.NET Core MVC, Razor, and Razor tag-helpers. Furthermore, you will also learn how to localize that application in several languages, and finally how to publish it.

You will cover many different aspects of ASP.NET development including: how to optimize user interfaces, validate user input, how to write clean and maintainable code with dependency injection and configuration data, and a whole lot more.

By the end of this course, you will be able to build both a public website and a business application based on ASP.NET Core MVC, with advanced features such as caching, authentication, and authorizations, and while conforming to Microsoft best-practices.

ASP.NET Core MVC

We already used the `DisplayAttribute` to specify the display name of properties and the `DataTypeAttribute` to further constrain a property type, specifying if a `DateTime` represents a date, a time, or a full DateTime, etc.

The above attributes are used by the ASP.NET Core framework itself to decide how to render ViewModel properties. There are also other attributes supported by ASP.NET Core we can use to define further property features. They are not used directly by ASP.NET Core default tag helpers, but they are available in our views so we can use them in our view code or also, in the definition of our custom tag helpers. 

# MetaData and MetaData providers ##

All metadata collected by the framework is available in all views through the `ViewData.ModelExplorer` property. More specifically, `ViewData.ModelExplorer.Metadata` contains all metadata associated with the view ViewModel. Metadata is useful for deciding how to render simple properties, so we should use `ViewData.ModelExplorer.Metadata` only when the view ViewModel is a simple property.

When the view ViewModel is a complex type, we should use `ViewData.ModelExplorer.GetExplorerForProperty(string name)`, instead. It returns all `ModelExplorer` instances associated with each property of the ViewModel. The code below shows an example:

This lesson explains how we can use property attributes to specify features that can be used each time a ViewModel is rendered.

Razor Template Language

Razor Language Assessment

Tag Helpers

Tag Helpers Assessment

Controllers and ViewModels

Controllers Assessment

Validation and Metadata

Validation Assessment

Dependency Injection

Configuration and Options Framework

Localization and Globalization

Factoring out UI Logic

Authentication and Authorization

Advanced Topics Assessment

Publishing Your Web Application

Conclusion

Appendix

Metadata and Metadata Attributes