Releasing stuff is dangerous: you might break things, you might annoy your users or you could screw up in any number of entertaining ways. Feature flags are a great way to get functionality into production without quite so much risk. You can release your new feature to only a small subset of your users and then roll it out once you're happy that things aren't on fire. The way you define flags will depend on the requirements for roll out – sometimes a configuration setting is sufficient; sometimes you'll need per-user settings or something more complex. That's outside the scope of this article though – I'll leave that part up to you. Once you have your flags defined you want to start modifying content based on those flags. You coulds do that with a bunch of if statements but when we're talking about Razor it can get messy fast. Instead, wouldn't it be nice to wrap your new stuff in a special tag? Or if you want to display something only for users without the new feature? Click here to enable my new cool thing! Enable Now! Tag Helpers make this easy! The TagHelper Class Tag helpers allow you to write server-side code that manipulates the DOM during the render of a Razor view.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.

This article is related to


Development,ASP.NET,Core,.NET Core,c#,software-development,web,asp.net,razor