You're reading from C# 11 and .NET 7 – Modern Cross-Platform Development Fundamentals Start building websites and services with ASP.NET Core 7, Blazor, and EF Core 7

Product type Paperback

Published in Nov 2022

Publisher Packt

ISBN-13 9781803237800

Length 818 pages

Edition 7th Edition

Languages

Tools

.NET

Concepts

Server Side Web Development

Author (1):

Mark J. Price

View More author details

Table of Contents (19) Chapters

Preface

1. Hello, C#! Welcome, .NET!

2. Speaking C# FREE CHAPTER

3. Controlling Flow, Converting Types, and Handling Exceptions

4. Writing, Debugging, and Testing Functions

5. Building Your Own Types with Object-Oriented Programming

6. Implementing Interfaces and Inheriting Classes

7. Packaging and Distributing .NET Types

8. Working with Common .NET Types

9. Working with Files, Streams, and Serialization

10. Working with Data Using Entity Framework Core

11. Querying and Manipulating Data Using LINQ

12. Introducing Web Development Using ASP.NET Core

13. Building Websites Using ASP.NET Core Razor Pages

14. Building Websites Using the Model-View-Controller Pattern

15. Building and Consuming Web Services

16. Building User Interfaces Using Blazor

17. Epilogue

18. Index

Building web services using the ASP.NET Core Web API

Before we build a modern web service, we need to cover some background to set the context for this chapter.

Understanding web service acronyms

Although HTTP was originally designed to request and respond with HTML and other resources for humans to look at, it is also good for building services.

Roy Fielding stated in his doctoral dissertation, describing the Representational State Transfer (REST) architectural style, that the HTTP standard would be good for building services because it defines the following:

URIs to uniquely identify resources, like https://localhost:5001/api/products/23.
Methods to perform common tasks on those resources, like GET, POST, PUT, and DELETE.
The ability to negotiate the media type of content exchanged in requests and responses, such as XML and JSON. Content negotiation happens when the client specifies a request header like Accept: application/xml,*/*;q=0.8. The default...