Skip to content

Commit 49ecb7d

Browse files
zhiyuanliang-mszhiyuanliang-ms
committed
add references
1 parent 109b961 commit 49ecb7d

9 files changed

+109
-25
lines changed

‎articles/azure-app-configuration/concept-feature-management.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,5 +88,7 @@ Azure App Configuration provides a centralized repository for feature flags. You
8888

8989
## Next steps
9090

91+
To get a full feature rundown of .NET feature management library, see the following resource.
92+
9193
> [!div class="nextstepaction"]
92-
> [Add feature flags to an ASP.NET Core web app](./quickstart-feature-flag-aspnet-core.md)
94+
> [.NET Feature Management](./feature-management-dotnet-reference.md)

‎articles/azure-app-configuration/feature-management-dotnet-reference.md

Lines changed: 38 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,17 @@
11
---
2-
title: .NET feature management - Azure App Configuration
3-
description: Overview of .NET Feature Management library
2+
title: .NET feature flag management | Microsoft Docs
3+
titleSuffix: Azure App Configuration
4+
description: In this tutorial, you learn how to use feature flags in .NET apps. The feature management library provides various out-of-the-box solutions for application development, ranging from simple feature toggles to complex feature experimentation.
45
services: azure-app-configuration
56
author: zhiyuanliang-ms
67
ms.author: zhiyuanliang
78
ms.service: azure-app-configuration
9+
ms.devlang: csharp
810
ms.custom: devx-track-dotnet
911
ms.topic: tutorial
1012
ms.date: 05/22/2024
1113
zone_pivot_groups: feature-management
14+
#Customer intent: I want to control feature availability in my app by using the .NET Feature Manager library.
1215
---
1316

1417
# .NET Feature Management
@@ -323,10 +326,10 @@ By default, the feature manager retrieves feature flag configuration from the "F
323326

324327
> [!NOTE]
325328
> You can also specify that feature flag configuration should be retrieved from a different configuration section by passing the section to `AddFeatureManagement`. The following example tells the feature manager to read from a different section called "MyFeatureFlags" instead:
326-
327-
``` C#
328-
services.AddFeatureManagement(configuration.GetSection("MyFeatureFlags"));
329-
```
329+
>
330+
> ``` C#
331+
> services.AddFeatureManagement(configuration.GetSection("MyFeatureFlags"));
332+
> ```
330333
331334
### Dependency Injection
332335
@@ -1423,3 +1426,32 @@ To use an implementation of `IFeatureDefinitionProvider`, it must be added into
14231426
services.AddSingleton<IFeatureDefinitionProvider, InMemoryFeatureDefinitionProvider>()
14241427
.AddFeatureManagement()
14251428
```
1429+
1430+
## Next steps
1431+
1432+
To learn how to use feature flags in your applications, continue to the following quickstarts.
1433+
1434+
> [!div class="nextstepaction"]
1435+
> [.NET/.NET Framework Console App](./quickstart-feature-flag-dotnet.md)
1436+
1437+
> [!div class="nextstepaction"]
1438+
> [.NET Background Service](./quickstart-feature-flag-dotnet-background-service.md)
1439+
1440+
> [!div class="nextstepaction"]
1441+
> [ASP.NET Core](./quickstart-feature-flag-aspnet-core.md)
1442+
1443+
To learn how to use feature filters, continue to the following tutorials.
1444+
1445+
> [!div class="nextstepaction"]
1446+
> [Enable conditional features with feature filters](./howto-feature-filters.md)
1447+
1448+
> [!div class="nextstepaction"]
1449+
> [Enable features on a schedule](./howto-timewindow-filter.md)
1450+
1451+
> [!div class="nextstepaction"]
1452+
> [Roll out features to targeted audiences](./howto-targetingfilter.md)
1453+
1454+
To learn how to run experiments with variant feature flags, continue to the following tutorial.
1455+
1456+
> [!div class="nextstepaction"]
1457+
> [Run experiments with variant feature flags](./howto-feature-filters.md)

‎articles/azure-app-configuration/manage-feature-flags.md

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Use Azure App Configuration to manage feature flags"
2+
title: Use Azure App Configuration to manage feature flags
33
titleSuffix: Azure App Configuration
44
description: In this quickstart, you learn how to manage feature flags separately from your application by using Azure App Configuration.
55
services: azure-app-configuration
@@ -143,5 +143,18 @@ Feature flags created with the Feature manager are stored as regular key-values.
143143

144144
## Next steps
145145

146+
To learn how to use feature flags in your applications, continue to the following quickstarts.
147+
148+
> [!div class="nextstepaction"]
149+
> [.NET/.NET Framework Console App](./quickstart-feature-flag-dotnet.md)
150+
151+
> [!div class="nextstepaction"]
152+
> [.NET Background Service](./quickstart-feature-flag-dotnet-background-service.md)
153+
154+
> [!div class="nextstepaction"]
155+
> [ASP.NET Core](./quickstart-feature-flag-aspnet-core.md)
156+
157+
To get a full feature rundown of .NET feature management library, see the following resource.
158+
146159
> [!div class="nextstepaction"]
147-
> [Enable staged rollout of features for targeted audiences](./howto-targetingfilter-aspnet-core.md)
160+
> [.NET Feature Management](./feature-management-dotnet-reference.md)

‎articles/azure-app-configuration/quickstart-feature-flag-aspnet-core.md

Lines changed: 14 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
---
2-
title: Quickstart for adding feature flags to ASP.NET Core
3-
description: Add feature flags to ASP.NET Core apps and manage them using Azure App Configuration
2+
title: Quickstart for adding feature flags to ASP.NET Core apps
3+
titleSuffix: Azure App Configuration
4+
description: In this tutorial, you learn how to add feature flags to ASP.NET Core apps and manage them using Azure App Configuration
5+
services: azure-app-configuration
46
author: zhenlan
57
ms.service: azure-app-configuration
68
ms.devlang: csharp
@@ -183,22 +185,28 @@ Add a feature flag called *Beta* to the App Configuration store and leave **Labe
183185
In this quickstart, you added feature management capability to an ASP.NET Core app on top of dynamic configuration. The [Microsoft.FeatureManagement.AspNetCore](https://www.nuget.org/packages/Microsoft.FeatureManagement.AspNetCore) library offers rich integration for ASP.NET Core apps, including feature management in MVC controller actions, razor pages, views, routes, and middleware. For more information, continue to the following tutorial.
184186
185187
> [!div class="nextstepaction"]
186-
> [Use feature flags in ASP.NET Core apps](./use-feature-flags-dotnet-core.md)
188+
> [.NET Feature Management](./feature-management-dotnet-reference.md)
187189
188190
While a feature flag allows you to activate or deactivate functionality in your app, you may want to customize a feature flag based on your app's logic. Feature filters allow you to enable a feature flag conditionally. For more information, continue to the following tutorial.
189191
190192
> [!div class="nextstepaction"]
191-
> [Use feature filters for conditional feature flags](./howto-feature-filters-aspnet-core.md)
193+
> [Enable conditional features with feature filters](./howto-feature-filters.md)
192194
193195
Azure App Configuration offers built-in feature filters that enable you to activate a feature flag only during a specific period or to a particular targeted audience of your app. For more information, continue to the following tutorial.
194196
195197
> [!div class="nextstepaction"]
196-
> [Enable features for targeted audiences](./howto-targetingfilter-aspnet-core.md)
198+
> [Enable features on a schedule](./howto-timewindow-filter.md)
199+
200+
> [!div class="nextstepaction"]
201+
> [Roll out features to targeted audiences](./howto-targetingfilter.md)
197202
198203
To enable feature management capability for other types of apps, continue to the following tutorials.
199204
200205
> [!div class="nextstepaction"]
201-
> [Use feature flags in .NET apps](./quickstart-feature-flag-dotnet.md)
206+
> [Use feature flags in .NET/.NET framework console apps](./quickstart-feature-flag-dotnet.md)
207+
208+
> [!div class="nextstepaction"]
209+
> [Use feature flags in .NET background services](./quickstart-feature-flag-dotnet-background-service.md)
202210
203211
> [!div class="nextstepaction"]
204212
> [Use feature flags in Azure Functions](./quickstart-feature-flag-azure-functions-csharp.md)

‎articles/azure-app-configuration/quickstart-feature-flag-azure-functions-csharp.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -215,7 +215,7 @@ This project will use [dependency injection in .NET Azure Functions](../azure-fu
215215

216216
In this quickstart, you created a feature flag and used it with an Azure Functions app via the [Microsoft.FeatureManagement](https://www.nuget.org/packages/Microsoft.FeatureManagement/) library.
217217
218-
- Learn more about [feature management](./concept-feature-management.md)
218+
- Learn more about [feature management](./feature-management-dotnet-reference.md)
219219
- [Manage feature flags](./manage-feature-flags.md)
220220
- [Use conditional feature flags](./howto-feature-filters-aspnet-core.md)
221221
- [Enable staged rollout of features for targeted audiences](./howto-targetingfilter-aspnet-core.md)

‎articles/azure-app-configuration/quickstart-feature-flag-dotnet-background-service.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -176,7 +176,7 @@ Add a feature flag called *Beta* to the App Configuration store and leave **Labe
176176
To enable feature management capability for other types of apps, continue to the following tutorials.
177177
178178
> [!div class="nextstepaction"]
179-
> [Use feature flags in .NET console apps](./quickstart-feature-flag-dotnet.md)
179+
> [Use feature flags in .NET/.NET framework console apps](./quickstart-feature-flag-dotnet.md)
180180
181181
> [!div class="nextstepaction"]
182182
> [Use feature flags in ASP.NET Core apps](./quickstart-feature-flag-aspnet-core.md)
@@ -185,3 +185,8 @@ To learn more about managing feature flags in Azure App Configuration, continue
185185
186186
> [!div class="nextstepaction"]
187187
> [Manage feature flags in Azure App Configuration](./manage-feature-flags.md)
188+
189+
To get a full feature rundown of `Microsoft.FeatureManagement` package, see the following doc.
190+
191+
> [!div class="nextstepaction"]
192+
> [.NET Feature Management](./feature-management-dotnet-reference.md)

‎articles/azure-app-configuration/quickstart-feature-flag-dotnet.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -166,10 +166,21 @@ You can use Visual Studio to create a new console app project.
166166
167167
In this quickstart, you created a feature flag in App Configuration and used it with a console app. To learn how to dynamically update feature flags and other configuration values without restarting the application, continue to the next tutorial.
168168
169-
170169
> [!div class="nextstepaction"]
171170
> [Enable dynamic configuration in a .NET app](./enable-dynamic-configuration-dotnet-core.md)
172171
173172
> [!div class="nextstepaction"]
174173
> [Enable dynamic configuration in a .NET Framework app](./enable-dynamic-configuration-dotnet.md)
175174
175+
To enable feature management capability for other types of apps, continue to the following tutorials.
176+
177+
> [!div class="nextstepaction"]
178+
> [Use feature flags in .NET background services](./quickstart-feature-flag-dotnet-background-service.md)
179+
180+
> [!div class="nextstepaction"]
181+
> [Use feature flags in ASP.NET Core apps](./quickstart-feature-flag-aspnet-core.md)
182+
183+
To get a full feature rundown of `Microsoft.FeatureManagement` package, see the following doc.
184+
185+
> [!div class="nextstepaction"]
186+
> [.NET Feature Management](./feature-management-dotnet-reference.md)

‎articles/azure-app-configuration/run-experiments-aspnet-core.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -496,4 +496,12 @@ Any edit to a variant feature flag generates a new version of the experimentatio
496496
497497
## Next step
498498
499+
To learn more about experimentation, see the following resources.
500+
501+
> [!div class="nextstepaction"]
499502
> [Experimentation](./concept-experimentation.md)
503+
504+
To get a full feature rundown of `Microsoft.FeatureManagement` package, see the following doc.
505+
506+
> [!div class="nextstepaction"]
507+
> [.NET Feature Management](./feature-management-dotnet-reference.md)

‎articles/azure-app-configuration/use-feature-flags-dotnet-core.md

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,23 +2,27 @@
22
title: Tutorial for using feature flags in a .NET app | Microsoft Docs
33
description: In this tutorial, you learn how to implement feature flags in .NET apps.
44
services: azure-app-configuration
5-
author: maud-lv
5+
author: zhiyuanliang-ms
66
ms.service: azure-app-configuration
77
ms.devlang: csharp
88
ms.topic: tutorial
9-
ms.date: 02/20/2024
10-
ms.author: malev
9+
ms.date: 07/02/2024
10+
ms.author: zhiyuanliang
1111
ms.custom: devx-track-csharp, mvc, devx-track-dotnet
1212
#Customer intent: I want to control feature availability in my app by using the .NET Feature Manager library.
1313
---
1414

1515
# Tutorial: Use feature flags in an ASP.NET Core app
1616

17-
The .NET Feature Management libraries provide idiomatic support for implementing feature flags in a .NET or ASP.NET Core application. These libraries allow you to declaratively add feature flags to your code so that you don't have to manually write code to enable or disable features with `if` statements.
17+
The .NET feature management libraries provide idiomatic support for implementing feature flags in a .NET or ASP.NET Core application. These libraries allow you to declaratively add feature flags to your code so that you don't have to manually write code to enable or disable features with `if` statements.
1818

19-
The Feature Management libraries also manage feature flag lifecycles behind the scenes. For example, the libraries refresh and cache flag states, or guarantee a flag state to be immutable during a request call. In addition, the ASP.NET Core library offers out-of-the-box integrations, including MVC controller actions, views, routes, and middleware.
19+
The feature management libraries also manage feature flag lifecycles behind the scenes. For example, the libraries refresh and cache flag states, or guarantee a flag state to be immutable during a request call. In addition, the ASP.NET Core library offers out-of-the-box integrations, including MVC controller actions, views, routes, and middleware.
2020

21-
For the ASP.NET Core feature management API reference documentation, see [Microsoft.FeatureManagement Namespace](/dotnet/api/microsoft.featuremanagement).
21+
> [!NOTE]
22+
> For the lastest full feature rundown of .NET feature management libraries, please go to the following doc.
23+
>
24+
> [!div class="nextstepaction"]
25+
> [.NET Feature Management](./feature-management-dotnet-reference.md)
2226
2327
In this tutorial, you will learn how to:
2428

@@ -270,5 +274,6 @@ app.UseForFeature(featureName, appBuilder => {
270274
In this tutorial, you learned how to implement feature flags in your ASP.NET Core application by using the `Microsoft.FeatureManagement` libraries. For more information about feature management support in ASP.NET Core and App Configuration, see the following resources:
271275

272276
* [ASP.NET Core feature flag sample code](./quickstart-feature-flag-aspnet-core.md)
273-
* [Microsoft.FeatureManagement documentation](/dotnet/api/microsoft.featuremanagement)
277+
* [Microsoft.FeatureManagement Feature Reference](./feature-management-dotnet-reference.md)
278+
* [Microsoft.FeatureManagement API Reference](/dotnet/api/microsoft.featuremanagement)
274279
* [Manage feature flags](./manage-feature-flags.md)

0 commit comments

Comments
 (0)