Book Image

Modern Web Development with ASP.NET Core 3 - Second Edition

By : Ricardo Peres
Book Image

Modern Web Development with ASP.NET Core 3 - Second Edition

By: Ricardo Peres

Overview of this book

ASP.NET has been the preferred choice of web developers for a long time. With ASP.NET Core 3, Microsoft has made internal changes to the framework along with introducing new additions that will change the way you approach web development. This second edition has been thoroughly updated to help you make the most of the latest features in the framework, right from gRPC and conventions to Blazor, which has a new chapter dedicated to it. You’ll begin with an overview of the essential topics, exploring the Model-View-Controller (MVC) pattern, various platforms, dependencies, and frameworks. Next, you’ll learn how to set up and configure the MVC environment, before delving into advanced routing options. As you advance, you’ll get to grips with controllers and actions to process requests, and later understand how to create HTML inputs for models. Moving on, you'll discover the essential aspects of syntax and processes when working with Razor. You'll also get up to speed with client-side development and explore the testing, logging, scalability, and security aspects of ASP.NET Core. Finally, you'll learn how to deploy ASP.NET Core to several environments, such as Azure, Amazon Web Services (AWS), and Docker. By the end of the book, you’ll be well versed in development in ASP.NET Core and will have a deep understanding of how to interact with the framework and work cross-platform.
Table of Contents (26 chapters)
1
Section 1: The Fundamentals of ASP.NET Core 3
7
Section 2: Improving Productivity
14
Section 3: Advanced Topics
Appendix A: The dotnet Tool

Performing content negotiation

Content negotiation is theprocessby which the application returns data in a format that is requested by the client. This is usually done for API-style invocations, not requests that serve HTML. For example, a certain client might want data returned in JSON format, while others might prefer XML. ASP.NET Core supports this.

There are essentially two ways to achieve this:

  • Through a route or query string parameter
  • Through theAccept request header

The first approach lets you specify the format that you're interested in on the URL. Let's see how this works first:

  1. Say you have the following action method:
public Model Process() { ... }
  1. Let's forget whatModelactually is as it's just a POCO class that contains the properties you're interested in. It could be as simple as this:
public class Model
{
public...