Skip to content

Commit ac52319

Browse files
authored
add language slugs (#11216)
1 parent e9f43a5 commit ac52319

File tree

83 files changed

+6773
-6803
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

83 files changed

+6773
-6803
lines changed

xml/System.Web.Caching/SqlCacheDependency.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,7 @@
145145
146146
The database name passed to the `database` parameter must be defined in the application's Web.config file. For example, the following Web.config file defines a database named pubs for <xref:System.Web.Caching.SqlCacheDependency> change notifications.
147147
148-
```
148+
```xml
149149
<configuration>
150150
<connectionStrings>
151151
<add name="Pubs" connectionString="Data Source=(local); Initial Catalog=pubs; Integrated Security=true"; providerName="System.Data.SqlClient" />
@@ -247,7 +247,7 @@
247247
## Remarks
248248
The following markup shows a typical output-cache dependency directive.
249249
250-
```
250+
```xml
251251
<%@ OutputCache Duration="3600" SqlDependency="Northwind:Employees" VaryByParam="none" %>
252252
```
253253

xml/System.Web.Compilation/RouteUrlExpressionBuilder.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@
3636
## Examples
3737
The following example shows how to create markup that generates a hyperlink with a URL that is formatted for a route. The route is defined by using `http://www.contoso.com/search/{searchterm}` as the URL pattern.
3838
39-
```
39+
```xml
4040
<asp:HyperLink ID="HyperLink1" runat="server"
4141
NavigateUrl="<%$ RouteUrl:searchterm=Bicycles %>">
4242
Search for Bicycles
@@ -47,7 +47,7 @@
4747
4848
If the URL parameters provided to the `RouteUrl` expression are not sufficient to uniquely identify a route, you must include the route name. For example, if a Web application has two routes with `searchterm` as the sole URL parameter, the routes would have to be defined by using route names, and the hyperlink markup would resemble the following example:
4949
50-
```
50+
```xml
5151
<asp:HyperLink ID="HyperLink1" runat="server"
5252
NavigateUrl="<%$ RouteUrl:searchterm=Bicycles,
5353
routename=BasicSearchRoute %>">

xml/System.Web.Compilation/RouteValueExpressionBuilder.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@
3636
## Examples
3737
The following example shows how to use markup to display the value of the URL parameter `searchterm`. The route is defined by using `http://www.contoso.com/search/{searchterm}` as the URL pattern.
3838
39-
```
39+
```xml
4040
<asp:Label ID="Label1" runat="server"
4141
text="<%$ RouteValue:searchterm %>">
4242
</asp:Label>

xml/System.Web.Configuration/AuthorizationSection.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@
3535
> [!NOTE]
3636
> If you use the `credentials` section, be sure to follow the guidelines explained at [ASP.NET Authentication](https://learn.microsoft.com/previous-versions/aspnet/eeyk640h(v=vs.100)). For scalability and better security capability, it is recommended that you use an external database to store the users' credentials. For more information about building secure ASP.NET applications, see [Securing Your ASP.NET Application](https://learn.microsoft.com/archive/msdn-magazine/2012/january/asp-net-security-securing-your-asp-net-applications) and [Building Secure ASP.NET Applications: Authentication, Authorization, and Secure Communication](https://learn.microsoft.com/previous-versions/msp-n-p/ff649357(v=pandp.10)).
3737
38-
```
38+
```xml
3939
<authorization>
4040
<allow users="userName" roles="admin" verbs="post" />
4141
<deny users="*" verbs="post"/>

xml/System.Web.Configuration/ClientTarget.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@
3737
3838
The following code example shows how to declaratively specify values for several properties of the <xref:System.Web.Configuration.ClientTarget> class.
3939
40-
```
40+
```xml
4141
<clientTarget>
4242
<add alias=
4343
"uplevel"

xml/System.Web.Configuration/ClientTargetCollection.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@
4040
4141
The following example shows an excerpt from the configuration file.
4242
43-
```
43+
```xml
4444
<clientTarget>
4545
<add alias=
4646
"uplevel"

xml/System.Web.Configuration/ClientTargetSection.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@
3131
3232
The following code example shows how to declaratively specify values for several properties of the <xref:System.Web.Configuration.ClientTarget> class.
3333
34-
```
34+
```xml
3535
<clientTarget>
3636
<add alias=
3737
"uplevel" userAgent="Mozilla/5.0 (compatible;MSIE 6.0;Windows NT 5.1)"/>

xml/System.Web.Configuration/HttpCapabilitiesBase.xml

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2349,7 +2349,7 @@
23492349
## Remarks
23502350
Intended for internal use only. Some browsers require a meta-tag similar to the following for the browser to render properly.
23512351
2352-
```
2352+
```html
23532353
<META NAME="NAME" CONTENT="VALUE">
23542354
```
23552355
@@ -2421,14 +2421,12 @@
24212421
## Remarks
24222422
If `true`, server-control adapters insert the following tag into the HTML `<head>` element of a Web page:
24232423
2424-
```
2424+
```html
24252425
<META HTTP-EQUIV="CONTENT-TYPE" CONTENT=""; CHARSET="">
24262426
```
24272427
24282428
In this example, `CONTENT` is the value returned by the <xref:System.Web.Configuration.HttpCapabilitiesBase.PreferredRenderingMime%2A> property, and `charset` is the character encoding used.
24292429
2430-
2431-
24322430
## Examples
24332431
The following code example shows how to determine whether the browser requires an HTML `<meta>` element for which the `content-type` attribute is specified.
24342432
@@ -2724,7 +2722,7 @@
27242722
## Remarks
27252723
HTTP is a stateless protocol, and `VIEWSTATE` is one mechanism used to persist client changes across multiple requests. Each control on a Web page contains a <xref:System.Web.UI.Control.ViewState%2A> property, which represents the accumulation of any changes made by the client. In a Web Forms page, these changes are encoded in postback data as the `value` of an HTML `<input>` element with a `type` attribute of `hidden`. For example:
27262724
2727-
```
2725+
```html
27282726
<input type="hidden" name="__VIEWSTATE" value="t0PH_u56?cDxleHQ7P=" />
27292727
```
27302728
@@ -3147,7 +3145,7 @@
31473145
## Remarks
31483146
The `cache-control` value for the `http-equiv` attribute of HTML `<meta>` elements allows control over client caching of downloaded content, which includes Web pages. The following HTML fragment shows an example:
31493147
3150-
```
3148+
```html
31513149
<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE"/>
31523150
```
31533151
@@ -3157,7 +3155,7 @@
31573155
31583156
The <xref:System.Web.Configuration.HttpCapabilitiesBase.SupportsCacheControlMetaTag%2A> property also applies to the equivalent HTTP header form:
31593157
3160-
```
3158+
```txt
31613159
CACHE-CONTROL: NO-CACHE
31623160
```
31633161

xml/System.Web.Configuration/HttpHandlerAction.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@
3939
4040
The following configuration excerpt shows how to specify values declaratively for the `httpHandlers` section.
4141
42-
```
42+
```xml
4343
<httpHandlers>
4444
<add path="Calculator.custom"
4545
type="Samples.Aspnet.SystemWebConfiguration.Calculator, CalculatorHandler"

xml/System.Web.Configuration/HttpHandlersSection.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@
3535
3636
The following configuration excerpt shows how to specify values declaratively for the `httpHandlers` section.
3737
38-
```
38+
```xml
3939
<httpHandlers>
4040
<add path="Calculator.custom"
4141
type="Samples.Aspnet.SystemWebConfiguration.Calculator, CalculatorHandler"

xml/System.Web.Configuration/HttpModulesSection.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@
3434
3535
The following configuration file example shows how to specify values declaratively for the [httpModules Element (ASP.NET Settings Schema)](https://learn.microsoft.com/previous-versions/dotnet/netframework-4.0/9b9dh535(v=vs.100)) section.
3636
37-
```
37+
```xml
3838
<httpModules>
3939
<add name="TimerModule"
4040
type="Samples.Aspnet.Configuration.RequestTimeInterval, RequestTimeInterval Version=1.0.1557.23158, Culture=neutral,

xml/System.Web.Configuration/PagesEnableSessionState.xml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,11 +26,10 @@
2626
## Examples
2727
The following configuration file excerpt shows how to declaratively use values of the <xref:System.Web.Configuration.PagesEnableSessionState> enumeration to specify whether the session state is enabled.
2828
29-
```
29+
```xml
3030
<system.web>
3131
<pages enableSessionState="true" />
3232
</system.web>
33-
3433
```
3534
3635
The following code example shows how to use the <xref:System.Web.Configuration.PagesEnableSessionState> enumeration with the <xref:System.Web.Configuration.PagesSection> type.

xml/System.Web.Configuration/PagesSection.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@
3131
3232
The following configuration file example shows how to specify values declaratively for the [pages](https://learn.microsoft.com/previous-versions/dotnet/netframework-4.0/950xf363(v=vs.100)) section.
3333
34-
```
34+
```xml
3535
<system.web>
3636
<pages buffer="true"
3737
enableSessionState="true"

xml/System.Web.Configuration/PassportAuthentication.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@
3838
## Examples
3939
The following code example shows how to obtain the <xref:System.Web.Configuration.PassportAuthentication> object from the configuration file of an existing Web application. Also shown is a configuration example.
4040
41-
```
41+
```xml
4242
<authentication>
4343
<passport redirectUrl="Login.aspx"/>
4444
</authentication>

xml/System.Web.Configuration/SessionStateSection.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@
3333
3434
The following configuration file example shows how to specify values declaratively for the `sessionState` section.
3535
36-
```
36+
```xml
3737
<configuration>
3838
<system.web>
3939
<sessionState mode="InProc"

xml/System.Web.DynamicData/DynamicControl.xml

Lines changed: 21 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -76,28 +76,28 @@
7676
<a name="declarative_syntax"></a>
7777
## Declarative Syntax
7878
79-
```
79+
```xml
8080
<asp:DynamicControl
81-
    ApplyFormatInEditMode="True|False"
82-
    ConvertEmptyStringToNull="True|False"
83-
    CssClass="string"
84-
    DataField="string"
85-
    DataFormatString="string"
86-
    EnableViewState="True|False"
87-
    HtmlEncode="True|False"
88-
    ID="string"
89-
    Mode="Edit|Insert|ReadOnly"
90-
    NullDisplayText="string"
91-
    OnDataBinding="DataBinding event handler"
92-
    OnDisposed="Disposed event handler"
93-
    OnInit="Init event handler"
94-
    OnLoad="Load event handler"
95-
    OnPreRender="PreRender event handler"
96-
    OnUnload="Unload event handler"
97-
    runat="server"
98-
    UIHint="string"
99-
    ValidationGroup="string"
100-
    Visible="True|False"
81+
ApplyFormatInEditMode="True|False"
82+
ConvertEmptyStringToNull="True|False"
83+
CssClass="string"
84+
DataField="string"
85+
DataFormatString="string"
86+
EnableViewState="True|False"
87+
HtmlEncode="True|False"
88+
ID="string"
89+
Mode="Edit|Insert|ReadOnly"
90+
NullDisplayText="string"
91+
OnDataBinding="DataBinding event handler"
92+
OnDisposed="Disposed event handler"
93+
OnInit="Init event handler"
94+
OnLoad="Load event handler"
95+
OnPreRender="PreRender event handler"
96+
OnUnload="Unload event handler"
97+
runat="server"
98+
UIHint="string"
99+
ValidationGroup="string"
100+
Visible="True|False"
101101
>
102102
</asp:DynamicControl>
103103
```

xml/System.Web.DynamicData/DynamicField.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@
6060
<a name="declarative_syntax"></a>
6161
## Declarative Syntax
6262
63-
```
63+
```xml
6464
<asp:DynamicField
6565
AccessibleHeaderText="string"
6666
ApplyFormatInEditMode="true|false"

xml/System.Web.Management/WebFailureAuditEvent.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@
5858
5959
The following configuration excerpt shows how to enable ASP.NET to use the <xref:System.Web.Management.WebFailureAuditEvent> event.
6060
61-
```
61+
```xml
6262
<healthMonitoring
6363
enabled="true"
6464
heartBeatInterval="0">

xml/System.Web.Profile/ProfileGroupBase.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@
130130
## Examples
131131
The following Web.config file specifies a user profile that contains a group of properties with a group name of `Address`. The grouped properties generated for the <xref:System.Web.HttpContext.Profile%2A> property of the current <xref:System.Web.HttpContext> will be preceded by the group name, for example, `Profile.Address.Street`.
132132
133-
```
133+
```xml
134134
<configuration>
135135
<connectionStrings>
136136
<add name="SqlServices" connectionString="Data Source=localhost;Integrated Security=SSPI;Initial Catalog=aspnetdb;" />

xml/System.Web.Profile/ProfileManager.xml

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@
2626
2727
By default, the user profile is disabled for all ASP.NET applications. To enable the user profile, set the `enabled` attribute of the [profile](https://learn.microsoft.com/previous-versions/dotnet/netframework-4.0/ms164644(v%3dvs.100)) configuration element to true, as shown in the following example.
2828
29-
```
29+
```xml
3030
<configuration>
3131
<system.web>
3232
<profile enabled="true" />
@@ -38,7 +38,7 @@
3838
3939
A profile provider is used to store and retrieve properties in the user profile. The .NET Framework includes a <xref:System.Web.Profile.SqlProfileProvider> class that stores user profile properties in a SQL Server database. A <xref:System.Web.Profile.SqlProfileProvider> instance named `AspNetSqlProvider` is specified in the machine configuration as the default profile provider. The `AspNetSqlProvider` instance connects to the SQL Server database on the local Web server. You can specify a <xref:System.Web.Profile.SqlProfileProvider> that connects to another SQL Server as the default profile provider by using the [providers](https://learn.microsoft.com/previous-versions/dotnet/netframework-4.0/ms164654(v%3dvs.100)) configuration element and the `defaultProvider` attribute of the [profile](https://learn.microsoft.com/previous-versions/dotnet/netframework-4.0/ms164644(v%3dvs.100)) configuration element, as shown in the following example.
4040
41-
```
41+
```xml
4242
<configuration>
4343
<connectionStrings>
4444
<add name="SqlServices" connectionString=
@@ -142,7 +142,7 @@
142142
## Examples
143143
The following configuration file excerpt shows the [profile](https://learn.microsoft.com/previous-versions/dotnet/netframework-4.0/ms164644(v%3dvs.100)) element in the [system.web](/dotnet/framework/configure-apps/file-schema/web/system-web-element-web-settings) section of the Web.config file for an ASP.NET application. It sets the application's default profile provider to a <xref:System.Web.Profile.SqlProfileProvider> instance and sets the <xref:System.Web.Profile.ProfileManager.ApplicationName%2A> to `MyApplication`.
144144
145-
```
145+
```xml
146146
<profile enabled="true" defaultProvider="SqlProvider">
147147
<providers>
148148
<add name="SqlProvider"
@@ -191,7 +191,7 @@
191191
## Examples
192192
The following configuration file excerpt shows the [profile](https://learn.microsoft.com/previous-versions/dotnet/netframework-4.0/ms164644(v%3dvs.100)) element in the [system.web](/dotnet/framework/configure-apps/file-schema/web/system-web-element-web-settings) section of the Web.config file for an ASP.NET application. It specifies the application's default profile provider to a <xref:System.Web.Profile.SqlProfileProvider> instance and sets the `automaticSaveEnabled` attribute to `true`.
193193
194-
```
194+
```xml
195195
<profile enabled="true"
196196
automaticSaveEnabled="true"
197197
defaultProvider="SqlProvider">
@@ -477,7 +477,7 @@
477477
## Examples
478478
The following code example shows the [profile](https://learn.microsoft.com/previous-versions/dotnet/netframework-4.0/ms164644(v%3dvs.100)) element in the [system.web](/dotnet/framework/configure-apps/file-schema/web/system-web-element-web-settings) section of the Web.config file for an ASP.NET application where the user profile has been enabled.
479479
480-
```
480+
```xml
481481
<profile enabled="true" defaultProvider="SqlProvider">
482482
<providers>
483483
<add name="SqlProvider"
@@ -1161,7 +1161,7 @@
11611161
## Remarks
11621162
The <xref:System.Web.Profile.ProfileManager.Providers%2A> property references all of the profile providers enabled for an application, including providers added in the machine configuration and providers added in all Web.config files. You can control which profile providers are available for an application using the [providers](https://learn.microsoft.com/previous-versions/dotnet/netframework-4.0/ms164654(v%3dvs.100)) element of the [profile](https://learn.microsoft.com/previous-versions/dotnet/netframework-4.0/ms164644(v%3dvs.100)) section in the configuration file. For example, the following Web.config file removes the profile providers specified in parent configuration files and adds a <xref:System.Web.Profile.SqlProfileProvider> instance as the profile provider for the application.
11631163
1164-
```
1164+
```xml
11651165
<configuration>
11661166
<connectionStrings>
11671167
<add name="SqlServices" connectionString=

xml/System.Web.Routing/PageRouteHandler.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -158,7 +158,7 @@
158158
159159
Permissions are defined in the Web.config file, as shown in the following example:
160160
161-
```
161+
```xml
162162
<configuration>
163163
<location path="categoriespage.aspx">
164164
<system.web>

xml/System.Web.Routing/UrlRoutingHandler.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@
4242
4343
To register a customized handler for a particular file name extension, you must add that handler in the Web.config file. The following example shows how to register a customized handler for an ASP.NET Web site that is running in IIS 6.0 or IIS 7.0 in Classic mode.
4444
45-
```
45+
```xml
4646
<system.web>
4747
<httpHandlers>
4848
<add verb="*" path="*.abc"
@@ -53,7 +53,7 @@
5353
5454
The following example shows how to register the same handler for an ASP.NET Web site that is running in IIS 7.0.
5555
56-
```
56+
```xml
5757
<system.webServer>
5858
<handlers>
5959
<add verb="*" path="*.abc"

0 commit comments

Comments
 (0)