-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Other di containers #126
Comments
... 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. |
We're having this problem also. It would be great to see some guidance of how to use the |
Update: |
Fixed in release 3.1.0 |
I created a repo to demonstrate how to use Microsoft.FeatureManagement in third-party Di containers: https://github.com/zhiyuanliang-ms/FeatureManagement-Dotnet-DependencyInjection |
Hey Guys,
We're attempting to use this in a .net framework application that uses autofac. While attempting to register the various dependencies:
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?
The text was updated successfully, but these errors were encountered: