Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Real-World Web Development with .NET 9

You're reading from   Real-World Web Development with .NET 9 Build websites and services using mature and proven ASP.NET Core MVC, Web API, and Umbraco CMS

Arrow left icon
Product type Paperback
Published in Dec 2024
Publisher Packt
ISBN-13 9781835880388
Length
Edition 1st Edition
Languages
Arrow right icon
Toc

Table of Contents (16) Chapters Close

Real-World Web Development with .NET 9: Build websites and services using mature and proven ASP.NET Core MVC, Web API, and Umbraco CMS
1 Introducing Web Development Using Controllers FREE CHAPTER 2 Building Websites Using ASP.NET Core MVC 3 Model Binding, Validation, and Data Using EF Core 4 Building and Localizing Web User Interfaces 5 Authentication and Authorization 6 Performance Optimization Using Caching 7 Web User Interface Testing Using Playwright 8 Configuring and Containerizing ASP.NET Core Projects 9 Building Web Services Using ASP.NET Core Web API 10 Building Web Services Using ASP.NET Core OData 11 Building Web Services Using FastEndpoints 12 Web Service Integration Testing 13 Web Content Management Using Umbraco 14 Customizing and Extending Umbraco 15 Epilogue

Consuming web services using HTTP clients

Now that we have built and tried calling our Northwind service using tools, we will learn how to call it from any .NET app using the HttpClient class and its factory.

Understanding HttpClient

The easiest way to consume a web service is to use the HttpClient class. However, many people use it wrongly because it implements IDisposable and Microsoft's own documentation shows poor usage of it. See the book links in the GitHub repository for articles with more discussion of this.

Usually, when a type implements IDisposable, you should create it inside a using statement to ensure that it is disposed of as soon as possible. HttpClient is different because it is shared, reentrant, and partially thread-safe.

The problem has to do with how the underlying network sockets must be managed. The bottom line is that you should use a single instance of it for each HTTP endpoint that you consume during the life of your application. This will allow each HttpClient...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image