Learn how to work with advanced features of ASP.NET Core MVC.

Become an ASP.NET Core Developer

In this module, we'll learn how to create a modular, dynamic web application with ASP.NET Core MVC, Razor, and Razor tag-helpers. Furthermore, we’ll also learn how to localize that application in several languages and finally how to publish it.
 
We'll cover many aspects of ASP.NET development, including optimizing user interfaces, validating user input, writing clean and maintainable code with dependency injection and configuration data, and so on.

ASP.NET Core MVC

## What is ASP.NET Core? ##

**ASP.NET Core** is a .NET Core based framework for creating web applications. In turn, a framework may be defined as a logical architecture for creating a class of applications.

However, ASP.NET Core is much more than this, since, together with an architectural setting, it offers tools, libraries, and Razor. Razor is used for dynamically creating the content of web pages.

ASP.NET Core is the .NET Core / .NET 5 preferred choice for creating any type of web application. It is the evolution of the old ASP.NET running in the classic 4.x framework. Since it runs in .NET Core / .NET 5, applications are portable on a wide range of machines and operating systems that include Windows and most Linux distributions. Moreover, it has been optimized for **dynamic link library (DLL)** size and performance, and at the moment, it is probably the most performant and modular web framework available on the market.

Web applications are not necessarily-public web sites. They may also be private web sites running in a private network. Often also enterprise applications are implemented as private web sites because how easily they are deployed and updated.

Moreover, web applications are not necessarily made of web pages that are accessible with a web browser, but they may also contain the so-called web API, which is the web application way for interacting with other software instead of with humans.

This course focuses just on web applications designed for interacting with humans, and more specifically on Web applications that create HTML pages that users can visualize with a Browser.

## Different types of browser-based web applications ##

Browser-based applications somehow create HTML content that is rendered in a Web browser. This HTML content can be created directly in the user browser or in the web server by an ASP.NET Core application and then sent to the user browser.

The first case is an example of a **Single Page Applications** (or **SPA**) because the web server sends the browser just a unique HTML page that works as a kind of frame for the HTML created in the browser itself. This frame page contains all references needed to download the whole application code from the server. Once the application code is downloaded, it creates and updates the HTML pages content, as needed.

SPAs get the data to show to the user by interacting with Web APIs.

However this course will focus on the second case: we'll learn how to create the HTML that is rendered by the browser on the server-side. More specifically, on how to create the HTML content with ASP.NET Core and with a pattern called **MVC (Model View Controller)**. 

According to the **MVC** pattern, the user interface is split into **logical code** and **graphic code**. The logical code defines the pattern of interaction with the user, and what data to show on each HTML page, while the graphic code defines how to represent that data in HTML. The graphic code is enclosed in files called **views** while the logical code is enclosed in classes called **controllers**. Controllers and views communicate through objects called **models** that describe what data to represent in the HTML pages. We will describe the MVC pattern in detail later in this course.

# What is ASP.NET Core? ##

**ASP.NET Core** is a .NET Core based framework for creating web applications. In turn, a framework may be defined as a logical architecture for creating a class of applications.

However, ASP.NET Core is much more than this, since, together with an architectural setting, it offers tools, libraries, and Razor. Razor is used for dynamically creating the content of web pages.

ASP.NET Core is the .NET Core / .NET 5 preferred choice for creating any type of web application. It is the evolution of the old ASP.NET running in the classic 4.x framework. Since it runs in .NET Core / .NET 5, applications are portable on a wide range of machines and operating systems that include Windows and most Linux distributions. Moreover, it has been optimized for **dynamic link library (DLL)** size and performance, and at the moment, it is probably the most performant and modular web framework available on the market.

Web applications are not necessarily-public web sites. They may also be private web sites running in a private network. Often also enterprise applications are implemented as private web sites because how easily they are deployed and updated.

Moreover, web applications are not necessarily made of web pages that are accessible with a web browser, but they may also contain the so-called web API, which is the web application way for interacting with other software instead of with humans.

This course focuses just on web applications designed for interacting with humans, and more specifically on Web applications that create HTML pages that users can visualize with a Browser.

# Different types of browser-based web applications ##

Browser-based applications somehow create HTML content that is rendered in a Web browser. This HTML content can be created directly in the user browser or in the web server by an ASP.NET Core application and then sent to the user browser.

The first case is an example of a **Single Page Applications** (or **SPA**) because the web server sends the browser just a unique HTML page that works as a kind of frame for the HTML created in the browser itself. This frame page contains all references needed to download the whole application code from the server. Once the application code is downloaded, it creates and updates the HTML pages content, as needed.

SPAs get the data to show to the user by interacting with Web APIs.

However this course will focus on the second case: we'll learn how to create the HTML that is rendered by the browser on the server-side. More specifically, on how to create the HTML content with ASP.NET Core and with a pattern called **MVC (Model View Controller)**. 

According to the **MVC** pattern, the user interface is split into **logical code** and **graphic code**. The logical code defines the pattern of interaction with the user, and what data to show on each HTML page, while the graphic code defines how to represent that data in HTML. The graphic code is enclosed in files called **views** while the logical code is enclosed in classes called **controllers**. Controllers and views communicate through objects called **models** that describe what data to represent in the HTML pages. We will describe the MVC pattern in detail later in this course.

In this lesson, we will introduce ASP.NET Core and Razor, the ASP.NET Core language for creating dynamic web pages.

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

Appendix

Conclusion

Your First Razor page

What is ASP.NET Core?

Different types of browser-based web applications