Always will be ready notify the world about expectations as easy as possible: job change page
Apr 22

Feature Flags in .NET Core

Feature Flags in .NET Core

Feature flags, also known as feature toggles or feature flags, are a powerful technique used in software development to enable or disable specific features or code paths in your application without modifying the code itself. This allows you to release new features gradually, test them with a subset of users, or respond quickly to issues by toggling features on or off remotely.

Implement Feature Flag

  • add these packages but you should enable pre-release support because it’s not officially out yet even though it’s preview and it has many many download:
    add Microsoft.FeatureManagement package
    add Microsoft.FeatureManagement.AspNetCore package
  • in program.cs builder.Services.AddFeatureManagement();
  • in appsettings.json add this key FeatureManagement that has NewFeatureFlag with boolean value
"FeatureManagement": {
    "NewFeatureFlag": true
  • inject IFeatureManager in Controller Constructor
  • get flag value by await _featureManager.IsEnabledAsync(“NewFeatureFlag”)

Add IFeatureManager

Okay, what happens when you want to add an extra point that you want to test to a few people, we add FeatureGate(${featureFlagName})
look at the point of comment on FeatureGate


If we use .Net Core MVC, we can use tag helper <feature> for FeatureManagement:

@inject IFeatureManager
@addTagHelper *, Microsoft.FeatureManagement

<feature name="NewFeatureFlag" requirement="All">
  <a asp-action="GetCustomerNameForTest">Go to the GetCustomerNameForTest</a>

We can set environment variable by Environment.SetEnvironmentVariable() in program.cs before CreateBuilder"

Environment.SetEnvironmentVariable("FeatureManagement__NewFeatureFlag", "false", EnvironmentVariableTarget.Process);

Instead of using feature flag, we can use Environment variable

Using custom Feature Flag filters

Built in filters like PercentageFilter

// we should add this line in programs.cs
// add this percentage filter in appsetting.json
// "EnabledFor" is a property that take a list of parameters to configure the features.
//    “Percentage” is built-in with feature management library.
//    The “Value” which makes the feature flag decision.
"NewPercentageFilter": {
      "EnabledFor": [
          "Name": "Percentage", // this is name of built-in filter as we use PercentageFilter s
          "Parameters": { // PercentageFilter acccept
            "Value": 50
[FeatureGate("NewPercentageFilter")] // add this if you want to return only A if 'NewPercentageFilter' is true
public async Task<string> TestPercentageFilter()
  // check if NewPercentageFilter is true or not
  // Looks like the algorithms are switching between "A" and "B" on an average of 50 percentage
  var newAlgorithm = await _featureManager.IsEnabledAsync("NewPercentageFilter");

  return newAlgorithm ? "A" : "B";

Custom filter

Let say we need to execute endpoint on Microsoft Edge only,

  • make BrowserFilterSettings.cs that has ‘Allowed’ property and this property will use as Parameters of filter in appsetting.json
  • create custom filter BrowserFilter that implement IFeatureFilter and it’s FilterAlias ‘Browser’ this alias used in name of fitler key in appsetting.json
  • use IHttpContextAccessor to get information about the request and the current user.
  • add filter key in appsetting.json
public class BrowserFilterSettings
    // this property will use as Parameters of filter in appsetting.json
    public string[] Allowed { get; set; }
// create custom filter BrowserFilter that implement IFeatureFilter
// FilterAlias 'Browser' this alias used in name of fitler key in appsetting.json
// use IHttpContextAccessor to get information about the request and the current user.

public class BrowserFilter : IFeatureFilter
  private readonly IHttpContextAccessor _httpContextAccessor;

  public BrowserFilter(IHttpContextAccessor httpContextAccessor)
    _httpContextAccessor = httpContextAccessor;

  public Task<bool> EvaluateAsync(FeatureFilterEvaluationContext context)
    if (_httpContextAccessor.HttpContext != null)
      var userAgent = _httpContextAccessor.HttpContext.Request.Headers["User-Agent"].ToString();
      var _browserSettings = context.Parameters.Get<BrowserFilterSettings>();
      return Task.FromResult(_browserSettings.Allowed.Any(x => userAgent.Contains(x)));
      return Task.FromResult(false);
// add filter key in appsetting.json
// filter has name with same name of FilterAlias in BrowserFilter.cs
// filter has Parameters that has 'Allowed' same as BrowserFilterSettings.cs
  "BrowserFlag": {
      "EnabledFor": [
          "Name": "Browser",
          "Parameters": {
            "Allowed": [ "Edg" ]
// add FeatureGate with name of filter key that has define in appsetting.json
public async Task<ActionResult> ExcuteOnEdgeOnly()
    return Ok();
// add AddHttpContextAccessor in programs.cs
// add BrowserFilter in programs.cs

If we run application in google chrome browser, ExcuteOnEdgeOnly will return 404 but if we run application in Microsoft Edge browser, ExcuteOnEdgeOnly will execute successfully.

• • •



Aug 25, 2020
In my 2018 series, we covered EF Core Migrations to explain how to add, remove and apply Entity Framework Core Migrations in an ASP .NET Core web application project. In this article, we’ll continue to look at the newer 2020...
Nov 16, 2022
Author: Vipin Sharma
Need to communicate with multiple DBs in one application??Usually we don’t face such scenarios. However if such requirement comes in picture, we will see how easy it is to communicate with multiple DBs using repository pattern in .Net Core Web...
May 14, 2023
Author: Ravi Raghav
What is Kafka?Kafka is a distributed streaming platform developed by the Apache Software Foundation. It is designed to handle high-volume, real-time data streams and is commonly used for building data pipelines, stream processing applications, and real-time analytics.At its core, Kafka...
17 декабря 2014 г.
Краткий обзор .NET Core, как это соотносится с .NET Framework и что это все означает для кросс-платформенной разработки и разработки с открытым кодом.Взгляд назад – мотивация для .NET CoreПрежде всего, давайте оглянемся назад, чтобы понять, как платформа .NET была устроена...
Написать сообщение

© 1999–2024 WebDynamics
1980–... Sergey Drozdov
Area of interests: .NET Framework | .NET Core | C# | ASP.NET | Windows Forms | WPF | HTML5 | CSS3 | jQuery | AJAX | Angular | React | MS SQL Server | Transact-SQL | ADO.NET | Entity Framework | IIS | OOP | OOA | OOD | WCF | WPF | MSMQ | MVC | MVP | MVVM | Design Patterns | Enterprise Architecture | Scrum | Kanban