I had not worked with Microsoft.FeatureManagement before. My go-to with .NET has been FeatureToggle despite some of the odd syntax, because it makes spelling mistakes in configurations a non-issue by erroring early and by giving you strongly-typed solutions. I'll have to look into feature management more.
Lead Product Evangelist @Kentico, Founding partner @craftbrewingbiz. love to learn / teach web dev & software engineering, collecting vinyl records, mowing my lawn, craft 🍺
The error-ing early part is something I always lean towards when possible.
IoC containers like SimpleInjector verify your container by building everything in it 1 time at startup.
If you include your Feature configuration types in your container then the verification step will throw an exception if values can't be found in app settings or the database (assuming your classes guard against invalid parameters).
I haven't used FeatureToggle - I'll have to check it out.
Lead Product Evangelist @Kentico, Founding partner @craftbrewingbiz. love to learn / teach web dev & software engineering, collecting vinyl records, mowing my lawn, craft 🍺
I had not worked with Microsoft.FeatureManagement before. My go-to with .NET has been
FeatureToggledespite some of the odd syntax, because it makes spelling mistakes in configurations a non-issue by erroring early and by giving you strongly-typed solutions. I'll have to look into feature management more.The error-ing early part is something I always lean towards when possible.
IoC containers like
SimpleInjectorverify your container by building everything in it 1 time at startup.If you include your Feature configuration types in your container then the verification step will throw an exception if values can't be found in app settings or the database (assuming your classes guard against invalid parameters).
I haven't used
FeatureToggle- I'll have to check it out.Take a look and let me know what you think.
Safe .NET Feature Flags with FeatureToggle
Matt Eland ・ Sep 21 ・ 4 min read
I appreciate you writing that up!