Closed aberbegall closed 4 days ago
Hi, @aberbegall I think so. Since we are targeted on netstandard. Did you meet any specific problem while using this library in your .net framework project?
@zhiyuanliang-ms thanks for your reply. My main problem is how to set it up. I can add the nugget package but I am struggling to register the FeatureManager service with unity and how to specify the feature in the web.config as I do in appsettings.json...
I need to port this line from my test project (minimal API):
builder.Services.AddFeatureManagement().AddFeatureFilter<MyFeatureFilter>();
and this settings:
"FeatureManagement": {
"MyFeatureFilter": {
"EnabledFor": [
{
"Name": "MyFeatureFilter"
}
]
}
}
to the ASP.NET ways of working :) best would be to find an example or any code tip, many thanks
@aberbegall
Feature management is built on the .net configuration system. Here is our doc. Anyway, you need a IConfiguration
as the feature flag source.
The whole library is designed to be used with dependency injection. However, we also supports the non-DI usage.
Here we have a quickstart about how to use feature management in a non-DI way.
Can you also check #446
BTW, is that possible for you migrate configuration as this doc said?
@zhiyuanliang-ms thanks for the links and tips... I have a ASP.NET MVC project with Startup.cs with Owin and Unity IoC and the web.config required for the IIS app setup.
I hold plenty of web app settings in the web.config and I need to keep them there, cannot be migrated to appsettings.
I will examine the given links and see any possibilities to keep my web.config and sort out the Feature Flag declaration.
Closing this for now
Is it supported on net framework 4.8 project with web.config?