Merge pull request #36411 from dotnet/main

Author: guardrex

.github/workflows/blazor-hybrid-issue-processing.yml

@@ -17,7 +17,7 @@ jobs:
               issue_number: context.issue.number,
               owner: context.repo.owner,
               repo: context.repo.repo,
-              body: `### 🦃 ***Happy Thanksgiving!*** 🍽️
+              body: `### 🥳 ***Happy Holidays!*** 🍽️
 
             *Stand-by!* A green dinosaur 🦖 will be along shortly to assist.`
             })

.github/workflows/blazor-issue-processing.yml

@@ -23,21 +23,9 @@ jobs:
               issue_number: context.issue.number,
               owner: context.repo.owner,
               repo: context.repo.repo,
-              body: `### 🦃 ***Happy Thanksgiving!*** 🍽️
+              body: `### 🥳 ***Happy Holidays!*** 🍽️
 
-            This issue has been marked for triage on the Blazor Docs GitHub project, and I'll respond after the Thanksgiving holiday during the first week of December.
-
-            We only work on documentation on this repo. If you need product support, close this issue and seek assistance through one or more of the following support channels:
-
-            * [Stack Overflow (tagged: 'blazor')](https://stackoverflow.com/questions/tagged/blazor)
-            * [General ASP.NET Core Slack Team](https://aspnetcore.slack.com/join/shared_invite/zt-1mv5487zb-EOZxJ1iqb0A0ajowEbxByQ#/shared-invite/email)
-            * [Blazor Gitter](https://gitter.im/aspnet/Blazor)
-
-            If you think that you found a potential bug in the framework or have product feedback, close this issue and open a new issue for the ASP.NET Core product unit at [dotnet/aspnetcore issues](https://github.com/dotnet/aspnetcore/issues). Bug reports require a clear explanation of the problem, usually including a minimal repro project placed on GitHub for the product unit engineers to download and run. If you determine with the product unit that it isn't a bug but merely requires documentation, please re-open this docs issue and place a cross-link to your engineering issue discussion.
-
-            For problems or feedback on Visual Studio, close this issue and use the [**Report a Problem**](https://docs.microsoft.com/visualstudio/ide/how-to-report-a-problem-with-visual-studio) or [**Suggest a Feature**](https://docs.microsoft.com/visualstudio/ide/suggest-a-feature) processes from within VS, which open internal issues for the VS product unit. For more information, see [Visual Studio Feedback](https://developercommunity.visualstudio.com/home).
-
-            For problems with Visual Studio Code, close this issue and ask for support on community support forums. For bug reports and product feedback, open an issue on the [microsoft/vscode GitHub repo](https://github.com/microsoft/vscode/issues).`
+            *Stand-by!* A green dinosaur 🦖 will be along shortly to assist.`
             })
             await github.rest.issues.addLabels({
               issue_number: context.issue.number,

aspnetcore/blazor/components/integration.md

@@ -179,6 +179,12 @@ To support routable Razor components in Razor Pages apps:
 
    > [!NOTE]
    > The preceding example assumes that the <xref:Microsoft.AspNetCore.Components.Web.HeadOutlet> component and Blazor script (`_framework/blazor.server.js`) are rendered by the app's layout. For more information, see the [Configuration](#configuration) section.
+   >
+   > In .NET 10 or later, the Blazor script is included by the framework if the project contains at least one Razor component file (`.razor`). If your app requires the Blazor script but doesn't contain at least one component, add the following MSBuild property to the app's project file to force unconditional script inclusion:
+   >
+   > ```xml
+   > <RequiresAspNetWebAssets>true</RequiresAspNetWebAssets>
+   > ```
   
    <xref:Microsoft.AspNetCore.Mvc.Rendering.RenderMode> configures whether the `App` component:
 
@@ -260,6 +266,12 @@ To support routable Razor components in MVC apps:
 
    > [!NOTE]
    > The preceding example assumes that the <xref:Microsoft.AspNetCore.Components.Web.HeadOutlet> component and Blazor script (`_framework/blazor.server.js`) are rendered by the app's layout. For more information, see the [Configuration](#configuration) section.
+   >
+   > In .NET 10 or later, the Blazor script is included by the framework if the project contains at least one Razor component file (`.razor`). If your app requires the Blazor script but doesn't contain at least one component, add the following MSBuild property to the app's project file to force unconditional script inclusion:
+   >
+   > ```xml
+   > <RequiresAspNetWebAssets>true</RequiresAspNetWebAssets>
+   > ```
 
    <xref:Microsoft.AspNetCore.Mvc.Rendering.RenderMode> configures whether the `App` component:
 

aspnetcore/blazor/project-structure.md

@@ -70,11 +70,11 @@ The `Components/Pages` folder of the server project contains the app's routable
                    Add the angle brackets around the cross-link when
                    activating.
 
-:::moniker range=">= aspnetcore-10.0"
+moniker range=">= aspnetcore-10.0"
 
 The `NotFound` component (`NotFound.razor`) implements a Not Found page to display when content isn't found for a request path. For more information, see xref:blazor/fundamentals/navigation#not-found-responses.
 
-:::moniker-end
+moniker-end
 
 -->
 
@@ -332,19 +332,19 @@ Project structure:
                    Add the angle brackets around the cross-link when
                    activating.
 
-:::moniker-end
+moniker-end
 
-:::moniker range=">= aspnetcore-10.0"
+moniker range=">= aspnetcore-10.0"
 
 * `Pages` folder: Contains the Blazor app's routable Razor components (`.razor`). The route for each page is specified using the [`@page`](xref:mvc/views/razor#page) directive. The template includes the following components:
   * `Counter` component (`Counter.razor`): Implements the Counter page.
   * `Index` component (`Index.razor`): Implements the Home page.
   * `Weather` component (`Weather.razor`): Implements the Weather page.
   * `NotFound` component (`NotFound.razor`) Implements a Not Found page to display when content isn't found for a request path. For more information, see xref:blazor/fundamentals/navigation#not-found-responses.
 
-:::moniker-end
+moniker-end
 
-:::moniker range=">= aspnetcore-8.0 < aspnetcore-10.0"
+moniker range=">= aspnetcore-8.0 < aspnetcore-10.0"
 
 -->
 
@@ -357,9 +357,9 @@ Project structure:
                    https://github.com/dotnet/AspNetCore.Docs/pull/36145
                    is merged.
 
-:::moniker-end
+moniker-end
 
-:::moniker range=">= aspnetcore-8.0"
+moniker range=">= aspnetcore-8.0"
 
 -->
 

aspnetcore/blazor/security/additional-scenarios.md

@@ -551,7 +551,7 @@ Alternatively, the setting can be made in the app settings (`appsettings.json`)
 ```json
 {
   "AzureAd": {
-    "Authority": "https://login.microsoftonline.com/common/oauth2/v2.0/",
+    "Authority": "https://login.microsoftonline.com/common/oauth2/v2.0",
     ...
   }
 }