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:

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:

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

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

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.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more