You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Microsoft.Extension.DependencyInjection has new feature: Keyed Service from 8.0.0.
But it is not supported in IServiceProviderExtensions.RegisterTypesWithPrismContainer .
Then it throw exception :" Your service provider may not support keyed services "
I suggest add some code if "service.IsKeyedService".
dansiegel
changed the title
[BUG] Not support Keyed Service for .net 8
[Feature Request] Not support Keyed Service for .net 8
Feb 26, 2024
dansiegel
changed the title
[Feature Request] Not support Keyed Service for .net 8
[Feature Request] Add support Keyed Service for IServiceCollection
Feb 26, 2024
I ran into the same issue today. We updated the package Microsoft.Extensions.Http.Resilience from v8.1.0 to v8.2.0 and suddenly the application crashed at startup with 'This service descriptor is keyed. Your service provider may not support keyed services.'
If you are a Commercial Plus user this is now available starting with Prism.Container.DryIoc 9.0.92 or later.
Prism.Container.Microsoft already supports this.
Description
Microsoft.Extension.DependencyInjection has new feature: Keyed Service from 8.0.0.
But it is not supported in IServiceProviderExtensions.RegisterTypesWithPrismContainer .
Then it throw exception :" Your service provider may not support keyed services "
I suggest add some code if "service.IsKeyedService".
Steps to Reproduce
containerRegistry.RegisterServices(collection => collection.AddKeyedSingleton())
Platform with bug
WPF
Affected platforms
Windows
Did you find any workaround?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: