Repository navigation
Other di containers #126
Description
Hey Guys,
We're attempting to use this in a .net framework application that uses autofac. While attempting to register the various dependencies:
- ConfigurationFeatureDefinitionProvider
- FeatureManager
- EmptySessionManager
- FeatureManagerSnapshot
I've discovered that they are all sealed, is there any guidance or is it even possible to use this without resorting to reflection hacks?
Metadata
Metadata
Assignees
Labels
No labels
Activity
jeffcollaboro commentedon Jul 9, 2021
... or any other number of containers, Simple Injector etc, These classes are the public interface into feature flags they shouldn't be internal, we need to instantiate them to use this.
danielmackay commentedon Jul 18, 2023
We're having this problem also. It would be great to see some guidance of how to use the
FeatureManagerwith other IoC containers.zhiyuanliang-ms commentedon Nov 16, 2023
Update:
The PR #302 of exposing FeatureManager to public has been merged into main branch. Now the FeatureManagement should be compatible with other DI framework.
zhiyuanliang-ms commentedon Nov 23, 2023
Fixed in release 3.1.0
zhiyuanliang-ms commentedon Nov 29, 2023
I created a repo to demonstrate how to use Microsoft.FeatureManagement in third-party Di containers: https://github.com/zhiyuanliang-ms/FeatureManagement-Dotnet-DependencyInjection
:)