Skip to main content

Error when specifying a HttpMessageHandler - System.InvalidOperationException : No service for type 'RetryDelegatingHandler' has been registered.

I created a custom HttpMessageHandler to handle the retry logic in my HttpClient. (I know that I could have used Polly but what is the fun in that?)

I registered the HttpMessageHandler as part of my typed http client like this:

services.AddHttpClient<IGitHubService, GitHubService>(httpClient =>
{
httpClient.BaseAddress = new Uri("https://api.github.com/");
httpClient.AddHttpMessageHandler<RetryDelegatingHandler>();
// ...
});
view raw Startup.cs hosted with ❤ by GitHub

However when I ran my application it failed with the following error:

System.InvalidOperationException : No service for type ‘Reliability.RetryDelegatingHandler' has been registered.

  Stack Trace:

ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)

ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)

<>c__4`1.<AddHttpMessageHandler>b__4_1(HttpMessageHandlerBuilder b)

<>c__DisplayClass17_0.<CreateHandlerEntry>g__Configure|0(HttpMessageHandlerBuilder b)

<>c__DisplayClass3_0.<Configure>b__0(HttpMessageHandlerBuilder builder)

DefaultHttpClientFactory.CreateHandlerEntry(String name)

<.ctor>b__1()

Lazy`1.ViaFactory(LazyThreadSafetyMode mode)

Lazy`1.ExecutionAndPublication(LazyHelper executionAndPublication, Boolean useDefaultConstructor)

Lazy`1.CreateValue()

<7 more frames...>

CallSiteRuntimeResolver.VisitDisposeCache(ServiceCallSite transientCallSite, RuntimeResolverContext context)

CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)

CallSiteRuntimeResolver.Resolve(ServiceCallSite callSite, ServiceProviderEngineScope scope)

<>c__DisplayClass2_0.<RealizeService>b__0(ServiceProviderEngineScope scope)

ServiceProvider.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)

ServiceProvider.GetService(Type serviceType)

ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)

ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)

To use the generic AddHttpMessageHandler<T> I need to register the handler through the IoC container:

services.AddTransient<RetryDelegatingHandler>();

As an alternative I can use another overload and instantiate the handler myself:

services.AddHttpClient<IGitHubService, GitHubService>(httpClient =>
{
httpClient.BaseAddress = new Uri("https://api.github.com/");
httpClient.AddHttpMessageHandler(s=> new RetryDelegatingHandler());
// ...
});
view raw Startup.cs hosted with ❤ by GitHub

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...