Merge to Live

.github/workflows/merge-live.yml

@@ -0,0 +1,24 @@
+name: Merge to Live
+on:
+  push:
+    branches:
+      - main
+permissions:
+  contents: read
+  pull-requests: write
+env:
+  DOTNET_DOCS_HEAD: main
+  DOTNET_DOCS_BASE: live
+jobs:
+  default:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - run: |
+          if [ "$(gh pr list --base $DOTNET_DOCS_BASE --head $DOTNET_DOCS_HEAD --json id --jq ". | length")" -ne "0" ]; then
+            echo "::notice title=Skipping Workflow::A pull request for branch \"$DOTNET_DOCS_HEAD\" into branch \"$DOTNET_DOCS_BASE\" already exists."
+          else
+            gh pr create --base $DOTNET_DOCS_BASE --head $DOTNET_DOCS_HEAD --title "Merge to Live" --body "[AUTOMATED]"
+          fi
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/whats-new.yml

@@ -16,14 +16,16 @@ on:
 
 env:
   DOTNET_VERSION: '5.0.301' # set this to the dot net version to use
-  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
 # A workflow run is made up of one or more jobs that can run sequentially or in parallel
 jobs:
   # This workflow contains a single job called "create-what-is-new"
   create-what-is-new:
     # The type of runner that the job will run on
     runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
 
     # Steps represent a sequence of tasks that will be executed as part of the job
     steps:
@@ -38,7 +40,7 @@ jobs:
       - name: 'Print manual run reason'
         if: ${{ github.event_name == 'workflow_dispatch' }}
         run: |
-          echo 'Reason: ${{ github.event.inputs.reason }}'
+          echo "Reason: ${{ github.event.inputs.reason }}"
 
       # Print dotnet info
       - name: Display .NET info

.repoman.yml

@@ -53,6 +53,14 @@ issues:
             - labels-add: ["Blazor"]
             - projects-add: [35]
             - labels-remove: [":watch: Not Triaged"]
+        - check:
+            - type: metadata-comment
+              name: content source
+              value: "(?i).*main\/aspnetcore\/mvc\/views\/tag-helpers\/built-in\/persist-component-state.md"
+          pass:
+            - labels-add: ["Blazor"]
+            - projects-add: [35]
+            - labels-remove: [":watch: Not Triaged"]
 
         # If the word appears anywhere in the file name path, add the label
         - check:

.vscode/settings.json

@@ -25,5 +25,11 @@
         "TypeScript",
         "XML",
         "YAML"
-    ]
+    ],
+    "markdownlint.config": {
+        "MD028": false,
+        "MD025": {
+            "front_matter_title": ""
+        }
+    }
 }

aspnetcore/blazor/advanced-scenarios.md

@@ -5,7 +5,7 @@ description: Learn about advanced scenarios in Blazor, including how to incorpor
 monikerRange: '>= aspnetcore-3.1'
 ms.author: riande
 ms.custom: mvc
-ms.date: 03/16/2021
+ms.date: 11/09/2021
 no-loc: [Home, Privacy, Kestrel, appsettings.json, "ASP.NET Core Identity", cookie, Cookie, Blazor, "Blazor Server", "Blazor WebAssembly", "Identity", "Let's Encrypt", Razor, SignalR]
 uid: blazor/advanced-scenarios
 ---

aspnetcore/blazor/blazor-server-ef-core.md

@@ -5,7 +5,7 @@ description: Guidance for using EF Core in Blazor Server apps.
 monikerRange: '>= aspnetcore-3.1'
 ms.author: jeliknes
 ms.custom: mvc
-ms.date: 08/14/2020
+ms.date: 11/09/2021
 no-loc: [Home, Privacy, Kestrel, appsettings.json, "ASP.NET Core Identity", cookie, Cookie, Blazor, "Blazor Server", "Blazor WebAssembly", "Identity", "Let's Encrypt", Razor, SignalR]
 uid: blazor/blazor-server-ef-core
 ---

aspnetcore/blazor/components/built-in-components.md

@@ -5,7 +5,7 @@ description: Find information on Razor components built-into the Blazor framewor
 monikerRange: '>= aspnetcore-3.1'
 ms.author: riande
 ms.custom: mvc
-ms.date: 07/30/2021
+ms.date: 11/09/2021
 no-loc: [Home, Privacy, Kestrel, appsettings.json, "ASP.NET Core Identity", cookie, Cookie, Blazor, "Blazor Server", "Blazor WebAssembly", "Identity", "Let's Encrypt", Razor, SignalR]
 uid: blazor/components/built-in-components
 ---
@@ -22,6 +22,8 @@ The following built-in Razor components are provided by the Blazor framework:
 * [`DynamicComponent`](xref:blazor/components/dynamiccomponent)
 * [`ErrorBoundary`](xref:blazor/fundamentals/handle-errors#error-boundaries)
 * [`FocusOnNavigate`](xref:blazor/fundamentals/routing#focus-an-element-on-navigation)
+* [`HeadContent`](xref:blazor/components/control-head-content)
+* [`HeadOutlet`](xref:blazor/components/control-head-content)
 * [`InputCheckbox`](xref:blazor/forms-validation#built-in-form-components)
 * [`InputDate`](xref:blazor/forms-validation#built-in-form-components)
 * [`InputFile`](xref:blazor/file-uploads)
@@ -35,6 +37,7 @@ The following built-in Razor components are provided by the Blazor framework:
 * [`MainLayout`](xref:blazor/components/layouts#mainlayout-component)
 * [`NavLink`](xref:blazor/fundamentals/routing#navlink-and-navmenu-components)
 * [`NavMenu`](xref:blazor/fundamentals/routing#navlink-and-navmenu-components)
+* [`PageTitle`](xref:blazor/components/control-head-content)
 * [`Router`](xref:blazor/fundamentals/routing#route-templates)
 * [`Virtualize`](xref:blazor/components/virtualization)
 

aspnetcore/blazor/components/cascading-values-and-parameters.md

@@ -5,7 +5,7 @@ description: Learn how to flow data from an ancestor component to descendent com
 monikerRange: '>= aspnetcore-3.1'
 ms.author: riande
 ms.custom: mvc
-ms.date: 02/02/2021
+ms.date: 11/09/2021
 no-loc: [Home, Privacy, Kestrel, appsettings.json, "ASP.NET Core Identity", cookie, Cookie, Blazor, "Blazor Server", "Blazor WebAssembly", "Identity", "Let's Encrypt", Razor, SignalR]
 uid: blazor/components/cascading-values-and-parameters
 ---
@@ -28,15 +28,7 @@ The following `ThemeInfo` C# class is placed in a folder named `UIThemeClasses`
 
 `UIThemeClasses/ThemeInfo.cs`:
 
-```csharp
-namespace BlazorSample.UIThemeClasses
-{
-    public class ThemeInfo
-    {
-        public string ButtonClass { get; set; }
-    }
-}
-```
+[!code-csharp[](~/blazor/samples/6.0/BlazorSample_WebAssembly/UIThemeClasses/ThemeInfo.cs)]
 
 The following [layout component](xref:blazor/components/layouts) specifies theme information (`ThemeInfo`) as a cascading value for all components that make up the layout body of the <xref:Microsoft.AspNetCore.Components.LayoutComponentBase.Body> property. `ButtonClass` is assigned a value of [`btn-success`](https://getbootstrap.com/docs/5.0/components/buttons/), which is a Bootstrap button style. Any descendent component in the component hierarchy can use the `ButtonClass` property through the `ThemeInfo` cascading value.
 
@@ -52,7 +44,7 @@ The following component binds the `ThemeInfo` cascading value to a cascading par
 
 `Pages/ThemedCounter.razor`:
 
-[!code-razor[](~/blazor/samples/6.0/BlazorSample_WebAssembly/Pages/ThemedCounter.razor?highlight=2,15-17,23-24)]
+[!code-razor[](~/blazor/samples/6.0/BlazorSample_WebAssembly/Pages/ThemedCounter.razor)]
 
 ## Cascade multiple values
 
@@ -68,26 +60,22 @@ In the following example, two [`CascadingValue`](xref:Microsoft.AspNetCore.Compo
 </CascadingValue>
 
 @code {
-    private CascadingType parentCascadeParameter1;
+    private CascadingType? parentCascadeParameter1;
 
     [Parameter]
-    public CascadingType ParentCascadeParameter2 { get; set; }
-
-    ...
+    public CascadingType? ParentCascadeParameter2 { get; set; }
 }
 ```
 
 In a descendant component, the cascaded parameters receive their cascaded values from the ancestor component by <xref:Microsoft.AspNetCore.Components.CascadingValue%601.Name%2A>:
 
 ```razor
-...
-
 @code {
     [CascadingParameter(Name = "CascadeParam1")]
-    protected CascadingType ChildCascadeParameter1 { get; set; }
-    
+    protected CascadingType? ChildCascadeParameter1 { get; set; }
+
     [CascadingParameter(Name = "CascadeParam2")]
-    protected CascadingType ChildCascadeParameter2 { get; set; }
+    protected CascadingType? ChildCascadeParameter2 { get; set; }
 }
 ```
 
@@ -139,13 +127,13 @@ Child `Tab` components aren't explicitly passed as parameters to the `TabSet`. I
 
 @code {
     [Parameter]
-    public RenderFragment ChildContent { get; set; }
+    public RenderFragment? ChildContent { get; set; }
 
-    public ITab ActiveTab { get; private set; }
+    public ITab? ActiveTab { get; private set; }
 
     public void AddTab(ITab tab)
     {
-        if (ActiveTab == null)
+        if (ActiveTab is null)
         {
             SetActiveTab(tab);
         }
@@ -178,25 +166,25 @@ Descendent `Tab` components capture the containing `TabSet` as a cascading param
 
 @code {
     [CascadingParameter]
-    public TabSet ContainerTabSet { get; set; }
+    public TabSet? ContainerTabSet { get; set; }
 
     [Parameter]
-    public string Title { get; set; }
+    public string? Title { get; set; }
 
     [Parameter]
-    public RenderFragment ChildContent { get; set; }
+    public RenderFragment? ChildContent { get; set; }
 
-    private string TitleCssClass => 
-        ContainerTabSet.ActiveTab == this ? "active" : null;
+    private string? TitleCssClass => 
+        ContainerTabSet?.ActiveTab == this ? "active" : null;
 
     protected override void OnInitialized()
     {
-        ContainerTabSet.AddTab(this);
+        ContainerTabSet?.AddTab(this);
     }
 
     private void ActivateTab()
     {
-        ContainerTabSet.SetActiveTab(this);
+        ContainerTabSet?.SetActiveTab(this);
     }
 }
 ```
@@ -255,15 +243,7 @@ The following `ThemeInfo` C# class is placed in a folder named `UIThemeClasses`
 
 `UIThemeClasses/ThemeInfo.cs`:
 
-```csharp
-namespace BlazorSample.UIThemeClasses
-{
-    public class ThemeInfo
-    {
-        public string ButtonClass { get; set; }
-    }
-}
-```
+[!code-csharp[](~/blazor/samples/5.0/BlazorSample_WebAssembly/UIThemeClasses/ThemeInfo.cs)]
 
 The following [layout component](xref:blazor/components/layouts) specifies theme information (`ThemeInfo`) as a cascading value for all components that make up the layout body of the <xref:Microsoft.AspNetCore.Components.LayoutComponentBase.Body> property. `ButtonClass` is assigned a value of [`btn-success`](https://getbootstrap.com/docs/5.0/components/buttons/), which is a Bootstrap button style. Any descendent component in the component hierarchy can use the `ButtonClass` property through the `ThemeInfo` cascading value.
 
@@ -482,15 +462,7 @@ The following `ThemeInfo` C# class is placed in a folder named `UIThemeClasses`
 
 `UIThemeClasses/ThemeInfo.cs`:
 
-```csharp
-namespace BlazorSample.UIThemeClasses
-{
-    public class ThemeInfo
-    {
-        public string ButtonClass { get; set; }
-    }
-}
-```
+[!code-csharp[](~/blazor/samples/3.1/BlazorSample_WebAssembly/UIThemeClasses/ThemeInfo.cs)]
 
 The following [layout component](xref:blazor/components/layouts) specifies theme information (`ThemeInfo`) as a cascading value for all components that make up the layout body of the <xref:Microsoft.AspNetCore.Components.LayoutComponentBase.Body> property. `ButtonClass` is assigned a value of [`btn-success`](https://getbootstrap.com/docs/5.0/components/buttons/), which is a Bootstrap button style. Any descendent component in the component hierarchy can use the `ButtonClass` property through the `ThemeInfo` cascading value.
 

aspnetcore/blazor/components/class-libraries.md

@@ -5,7 +5,7 @@ description: Discover how components can be included in Blazor apps from an exte
 monikerRange: '>= aspnetcore-3.1'
 ms.author: riande
 ms.custom: mvc
-ms.date: 04/07/2021
+ms.date: 11/09/2021
 no-loc: [Home, Privacy, Kestrel, appsettings.json, "ASP.NET Core Identity", cookie, Cookie, Blazor, "Blazor Server", "Blazor WebAssembly", "Identity", "Let's Encrypt", Razor, SignalR]
 uid: blazor/components/class-libraries
 ---
@@ -170,7 +170,13 @@ Alternatively, add a [`@using`](xref:mvc/views/razor#using) directive and use th
 <Component1 />
 ```
 
-For library components that use [CSS isolation](xref:blazor/components/css-isolation), the component styles are automatically made available to the consuming app. There's no need to link the library's individual component stylesheets in the app that consumes the library. For the preceding examples, `Component1`'s stylesheet (`Component1.razor.css`) is included automatically.
+For library components that use [CSS isolation](xref:blazor/components/css-isolation), the component styles are automatically made available to the consuming app. There's no need to manually link or import the library's individual component stylesheets or its bundled CSS file in the app that consumes the library. The app uses CSS imports to reference the RCL's bundled styles. The bundled styles aren't published as a static web asset of the app that consumes the library. For a class library named `ClassLib` and a Blazor app with a `BlazorSample.styles.css` stylesheet, the RCL's stylesheet is imported at the top of the app's stylesheet automatically at build time:
+
+```css
+@import '_content/ClassLib/ClassLib.bundle.scp.css';
+```
+
+For the preceding examples, `Component1`'s stylesheet (`Component1.razor.css`) is bundled automatically.
 
 `Component1.razor.css` in the `ComponentLibrary` RCL:
 
@@ -334,6 +340,10 @@ Blazor WebAssembly and RCL projects *automatically* enable browser compatibility
 When authoring a library, indicate that a particular API isn't supported in browsers by specifying `browser` to <xref:System.Runtime.Versioning.UnsupportedOSPlatformAttribute>:
 
 ```csharp
+using System.Runtime.Versioning;
+
+...
+
 [UnsupportedOSPlatform("browser")]
 private static string GetLoggingDirectory()
 {
@@ -521,7 +531,13 @@ Alternatively, add a [`@using`](xref:mvc/views/razor#using) directive and use th
 <Component1 />
 ```
 
-For library components that use [CSS isolation](xref:blazor/components/css-isolation), the component styles are automatically made available to the consuming app. There's no need to link the library's individual component stylesheets in the app that consumes the library. For the preceding examples, `Component1`'s stylesheet (`Component1.razor.css`) is included automatically.
+For library components that use [CSS isolation](xref:blazor/components/css-isolation), the component styles are automatically made available to the consuming app. There's no need to manually link or import the library's individual component stylesheets or its bundled CSS file in the app that consumes the library. The app uses CSS imports to reference the RCL's bundled styles. The bundled styles aren't published as a static web asset of the app that consumes the library. For a class library named `ClassLib` and a Blazor app with a `BlazorSample.styles.css` stylesheet, the RCL's stylesheet is imported at the top of the app's stylesheet automatically at build time:
+
+```css
+@import '_content/ClassLib/ClassLib.bundle.scp.css';
+```
+
+For the preceding examples, `Component1`'s stylesheet (`Component1.razor.css`) is bundled automatically.
 
 `Component1.razor.css` in the `ComponentLibrary` RCL: