Dynamically enabling features with Feature Flags in .NET Core 3.1

[@whoiam6395]

You are best Asp.net core programmer!

[@jinalpatel9154]

Nice explanation. It is good solution provided use with care otherwise there may be chances too many branches in code and also dependency between feature is question. Like in order to feature 2 to work feature 1 must be available.

[@renatorcribeiro]

Nick Chapsas, você é muito bom mesmo, aprendo muito com seus videos.

[@yashpaljamra5545]

Great , thanks for sharing asp.net core series.

[@Mo-ef9yt]

Great video, but it would be nice with a database version.

[@BeLKa4444]

Great content, great video. 11/10

[@hachapuri1229]

What is the difference between using this "Feature Flags" and the typical Options pattern

[@emilsimonyan2818]

Great, thanks for video

[@talkathiriify]

Great! Thank you very much.

[@imtiazahmeddahar3744]

I like it but there is still hard coding features, there must be any option so we can add update or remove dynamically, like we do with users

[@mckchenthil]

How to manage feature flag in DB. Nowadays even appsettings are deployed through deployment pipeline. Is there any build in UI for managing feature flags similar to SwaggerUI

[@Rohit-nn9ky]

How are the changes getting reflected without re-compiling or re-building the Solution ?

[@DungNguyen-eg7ss]

thanks you

[@PankajNikam]

Can we target features based on customer level like if the customer is premium, then we show certain features and if the customer is not, we hide it?

[@mohanm8396]

what if i want to modify the value dynamically without deploying app again ?

[@alexanlp]

Can i use this with configuration in a database?

[@nedbog]

Nick, how do you obfuscate these configs, not to be altered by clients, so they can get a new feature for free?

[@DoorThief]

How well would this work for a Xamarin application?

[@nickchapsas]

I've never worked with Xamarin so I wouldn't be able to tell you

[@DamianWalczak]

what IDE are you using

[@nickchapsas]

I am using JetBrains Rider

[@clearlyunwell]

👍🏽

[@dotnetdevni]

But if you creating a Software as a service that means that your user could just turn the features on and off that's a big security risk, what is advance over this to storing bits in the database least that is more secure true its nice it gives you a method but you could always do that urserlf in code.

[@PelFox]

Generally you control these in the deployment pipeline.

[@imtiazdahar8451]

these features are still hard coded. i want to make them dynamic so i can turn on and off them from database (table). Would you like to make a video for dynamic feature toggle.

[@petertragardh4571]

Feature flags and breaking database changes. This is something nobody talks about. Is this a subject for you?

[@teriyakov]

Thanks for the thorough video but this functionality can be achieved without a nugget package. Why would you use this instead of the standard way (drive feature functionality from a flag set in appsettings/database/ arbitrary condition in the back end)?

[@nickchapsas]

Because the feature management package has some really cool functionality and extensibility which we will take a look at the next video allowing for some really flexible flags

[@teriyakov]

@@nickchapsas Ok, cool. Looking forward to it. Thanks for this series btw 👊😎

[@Endomorphism]

*Don't reinvent the wheel*

[@shreyasjejurkar1233]

You are noiceeeee!