Edition 0 Updated to asp. Net core 0

Use your Typed Client classes 
Finally, once you have your typed classes implemented, you can have them registered and configured 
with 
AddHttpClient()
. After that you can use them wherever services are injected by DI, such as in 
Razor page code or an MVC web app controller, shown in the below code from eShopOnContainers: 
namespace
Microsoft.
eShopOnContainers
.
WebMVC
.
Controllers
{ 
public
class
CatalogController : Controller 
{ 
private
ICatalogService _catalogSvc; 
public
CatalogController
(ICatalogService catalogSvc) => 
_catalogSvc = catalogSvc; 
public
async Task 
Index
(
int
? BrandFilterApplied, 
int
? TypesFilterApplied, 

---

305 
CHAPTER 7 | Implement resilient applications 
int
? page, 
[FromQuery]
string
errorMsg) 
{ 
var
itemsPage = 
10
; 
var
catalog = await _catalogSvc.
GetCatalogItems
(page ?? 
0
, 
itemsPage, 
BrandFilterApplied, 
TypesFilterApplied); 
//… Additional c
ode
} 
} 
} 
Up to this point, the above code snippet only shows the example of performing regular HTTP 
requests. But the ‘magic’ comes in the following sections where it shows how all the HTTP requests 
made by 
HttpClient
can have resilient policies such as retries with exponential backoff, circuit 
breakers, security features using auth tokens, or even any other custom feature. And all of these can 
be done just by adding policies and delegating handlers to your registered Typed Clients. 
Additional resources 
•
HttpClient guidelines for .NET
https://learn.microsoft.com/en-us/dotnet/fundamentals/networking/http/httpclient-guidelines
 
•