You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-app-configuration/quickstart-feature-flag-aspnet-core.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,9 +13,9 @@ ms.author: zhenlwa
13
13
14
14
# Quickstart: Add feature flags to an ASP.NET Core app
15
15
16
-
In this quickstart, you will create a feature flag in Azure App Configuration and use it to dynamically control the availability of a new web page in an ASP.NET Core app without restarting or redeploying it.
16
+
In this quickstart, you'll create a feature flag in Azure App Configuration and use it to dynamically control the availability of a new web page in an ASP.NET Core app without restarting or redeploying it.
17
17
18
-
The feature management support extends the dynamic configuration feature in App Configuration. The example in this quickstart builds on the ASP.NET Core app introduced in the dynamic configuration tutorial. Before you continue, finish the [quickstart](./quickstart-aspnet-core-app.md) and the [tutorial](./enable-dynamic-configuration-aspnet-core.md) to create an ASP.NET Core app with dynamic configuration first.
18
+
The feature management support extends the dynamic configuration feature in App Configuration. The example in this quickstart builds on the ASP.NET Core app introduced in the dynamic configuration tutorial. Before you continue, finish the [quickstart](./quickstart-aspnet-core-app.md), and the [tutorial](./enable-dynamic-configuration-aspnet-core.md) to create an ASP.NET Core app with dynamic configuration first.
19
19
20
20
## Prerequisites
21
21
@@ -164,7 +164,7 @@ Leave the rest of fields empty for now. Select **Apply** to save the new feature
164
164
<h1>This is the beta website.</h1>
165
165
```
166
166
167
-
Open *Beta.cshtml.cs*, and add `FeatureGate` attribute to the `BetaModel` class. The `FeatureGate` attribute ensures the *Beta* page is accessible only when the *Beta* feature flag is enabled. If the *Beta* feature flag is not enabled, the page will return 404 Not Found.
167
+
Open *Beta.cshtml.cs*, and add `FeatureGate` attribute to the `BetaModel` class. The `FeatureGate` attribute ensures the *Beta* page is accessible only when the *Beta* feature flag is enabled. If the *Beta* feature flag isn't enabled, the page will return 404 Not Found.
168
168
169
169
```csharp
170
170
using Microsoft.AspNetCore.Mvc.RazorPages;
@@ -222,7 +222,7 @@ Leave the rest of fields empty for now. Select **Apply** to save the new feature
222
222
223
223

224
224
225
-
1. Select the *Beta* menu. It will bring you to the beta website that you just enabled dynamically.
225
+
1. Select the *Beta* menu. It will bring you to the beta website that you enabled dynamically.
226
226
227
227

0 commit comments