So, you have decided to use Feature Toggling as your branching strategy. You don’t want the hassle of merging and branching and are confident that developers and testers can handle the additional complexity that comes with Feature Toggles. The next step is to decided how to go about using toggles. The simplest and most popular method of doing is to have feature toggles set in configuration files
Ideally, you would want a library that would take care of feature toggling. All you would need to do is to define the features and their toggle value in the configuration file and be able to check if a feature is available with a simple check. Some thing which for a configuration like below
<featureConfiguration>
<features>
<add name="PrivateProfiles" toggle="on" />
<add name="Photosharing" toggle="off" />
<add name="Videos" toggle="1" />
<add name="bookmarks" toggle="true" />
</features>
</featureConfiguration>
would allow having code like following
if (FeatureManager.HasFeature("PrivateProfiles")){
…
}
Having looked around, there were three libraries of note already available, which were
This blog post gives a good comparison of them and their usability. Having used all three, I felt that all of them, though thorough, were overly complicated for the very simple scenario that I wanted to use. For example, NFeature requires you to create enumerations for all features added in configuration file.
I decided to create a new very simple feature toggling library. https://github.com/hamidshahid/FeatureToggler
The library is available as NuGet. Simply type “Install-package FeatureToggler” in the package manager window of your application. It will add references, add a configuration section in your configuration files and adds a few sample features in your configuration file.
Once you have the reference added, simply add features in the features collection and use them in your code using the FeatureManager.HasFeature(“”) method. Happy Coding!!
No comments:
Post a Comment