|
| 1 | +--- |
| 2 | +title: .NET Feature Management |
| 3 | +description: Overview of .NET Feature Management library |
| 4 | +author: zhiyuanliang-ms |
| 5 | +ms.author: zhiyuanliang |
| 6 | +ms.service: azure-app-configuration |
| 7 | +ms.topic: tutorial |
| 8 | +ms.date: 05/22/2024 |
| 9 | +zone_pivot_groups: feature-management |
| 10 | +--- |
| 11 | + |
| 12 | +# .NET Feature Management |
| 13 | + |
| 14 | +.NET feature management library provides a way to develop and expose application functionality based on features. Many applications have special requirements when a new feature is developed such as when the feature should be enabled and under what conditions. This library provides a way to define these relationships, and also integrates into common .NET code patterns to make exposing these features possible. |
| 15 | + |
| 16 | +:::zone target="docs" pivot="stable-version" |
| 17 | + |
| 18 | +[](https://www.nuget.org/packages/Microsoft.FeatureManagement) |
| 19 | +[](https://www.nuget.org/packages/Microsoft.FeatureManagement.AspNetCore) |
| 20 | + |
| 21 | +:::zone-end |
| 22 | + |
| 23 | +:::zone target="docs" pivot="preview-version" |
| 24 | + |
| 25 | +[](https://www.nuget.org/packages/Microsoft.FeatureManagement/4.0.0-preview3) |
| 26 | +[](https://www.nuget.org/packages/Microsoft.FeatureManagement.AspNetCore/4.0.0-preview3) |
| 27 | +[](https://www.nuget.org/packages/Microsoft.FeatureManagement.Telemetry.ApplicationInsights/4.0.0-preview3) |
| 28 | +[](https://www.nuget.org/packages/Microsoft.FeatureManagement.Telemetry.ApplicationInsights.AspNetCore/4.0.0-preview3) |
| 29 | + |
| 30 | +:::zone-end |
| 31 | + |
| 32 | +Feature flags provide a way for .NET and ASP.NET Core applications to turn features on or off dynamically. Developers can use feature flags in simple use cases like conditional statements to more advanced scenarios like conditionally adding routes or MVC filters. Feature flags are built on top of the .NET Core configuration system. Any .NET Core configuration provider is capable of acting as the backbone for feature flags. |
| 33 | + |
| 34 | +Here are some of the benefits of using .NET feature management library: |
| 35 | + |
| 36 | +* A common convention for feature management |
| 37 | +* Low barrier-to-entry |
| 38 | + * Built on `IConfiguration` |
| 39 | + * Supports JSON file feature flag setup |
| 40 | +* Feature Flag lifetime management |
| 41 | + * Configuration values can change in real-time; feature flags can be consistent across the entire request |
| 42 | +* Simple to Complex Scenarios Covered |
| 43 | + * Toggle on/off features through declarative configuration file |
| 44 | + * Dynamically evaluate state of feature based on call to server |
| 45 | +* API extensions for ASP.NET Core and MVC framework |
| 46 | + * Routing |
| 47 | + * Filters |
| 48 | + * Action Attributes |
| 49 | + |
| 50 | + The .NET feature management library is open source. For more information, visit the [GitHub repo](https://github.com/microsoft/FeatureManagement-Dotnet). |
0 commit comments