AspNetFlags 0.1.0

dotnet add package AspNetFlags --version 0.1.0
                    
NuGet\Install-Package AspNetFlags -Version 0.1.0
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="AspNetFlags" Version="0.1.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="AspNetFlags" Version="0.1.0" />
                    
Directory.Packages.props
<PackageReference Include="AspNetFlags" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add AspNetFlags --version 0.1.0
                    
#r "nuget: AspNetFlags, 0.1.0"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package AspNetFlags@0.1.0
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=AspNetFlags&version=0.1.0
                    
Install as a Cake Addin
#tool nuget:?package=AspNetFlags&version=0.1.0
                    
Install as a Cake Tool

AspNetFlags

NuGet License: MIT

Feature flags with a toggle UI at /_flags, stored locally. No SaaS account, no SDK keys. Flags appear the first time your code checks them, so you flip them without declaring anything up front. Part of the AspNetDebugDashboard suite.

Flags

Install

dotnet add package AspNetFlags

Setup

using AspNetFlags;

builder.Services.AddFlags();   // 1. register
var app = builder.Build();
app.UseFlags();                // 2. serve /_flags (no-op outside Development)

Checking flags

Inject IFeatureFlags and gate whatever you want:

public class CheckoutController(IFeatureFlags flags)
{
    public IActionResult Index() =>
        flags.IsEnabled("new-checkout") ? View("NewCheckout") : View("Checkout");
}

The first check for an unknown flag registers it (off) so it shows up at /_flags. Flip it there and the next check returns the new value.

What you get

/_flags lists every flag your app has touched, each with an on/off switch and when it last changed. Toggling persists immediately; changes take effect on the next IsEnabled call. You can also add a flag by name or delete one from the page, and filter the list once it grows. The page polls so flags discovered by other requests show up live.

Configuration

builder.Services.AddFlags(o =>
{
    o.BasePath = "/_flags";       // dashboard route
    o.DatabasePath = "flags.db";  // local LiteDB store
    o.AutoDiscover = true;        // off = a flag must exist before it can be toggled
});

License

MIT.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
0.1.0 48 6/17/2026