Book Image

Customizing ASP.NET Core 6.0 - Second Edition

By : Jürgen Gutsch
Book Image

Customizing ASP.NET Core 6.0 - Second Edition

By: Jürgen Gutsch

Overview of this book

ASP.NET Core is packed full of hidden features for building sophisticated web applications – but if you don’t know how to customize it, you’re not making the most of its capabilities. Customizing ASP.NET Core 6.0 is a book that will teach you all about tweaking the knobs at various layers and take experienced programmers’ skills to a new level. This updated second edition covers the latest features and changes in the .NET 6 LTS version, along with new insights and customization techniques for important topics such as authentication and authorization. You’ll also learn how to work with caches and change the default behavior of ASP.NET Core apps. This book will show you the essential concepts relating to tweaking the framework, such as configuration, dependency injection, routing, action filters, and more. As you progress, you'll be able to create custom solutions that meet the needs of your use case with ASP.NET Core. Later chapters will cover expert techniques and best practices for using the framework for your app development needs, from UI design to hosting. Finally, you'll focus on the new endpoint routing in ASP.NET Core to build custom endpoints and add third-party endpoints to your web apps for processing requests faster. By the end of this book, you'll be able to customize ASP.NET Core to develop better, more robust apps.
Table of Contents (18 chapters)

Introducing OutputFormatter objects

In ASP.NET Core, OutputFormatters are classes that transform your existing data into different formats to send it through HTTP to clients. The web API uses a default OutputFormatters to turn objects into JSON, which is the default format to send structured data. Other built-in formatters include an XML formatter and a plain text formatter.

With so-called content negotiation, clients are able to decide which format they want to retrieve. The client needs to specify the content type of the format in the Accept header. Content negotiation is implemented in ObjectResult.

By default, the web API always returns JSON, even if you accept text/XML in the header. This is why the built-in XML formatter is not registered by default.

There are two ways to add XmlSerializerOutputFormatter to ASP.NET Core:

  • The first is shown in the following code snippet:
    builder.Services.AddControllers()
        .AddXmlSerializerFormatters();
  • ...