Merge pull request #35681 from dotnet/main

Author: guardrex

.openpublishing.redirection.json

@@ -1522,6 +1522,11 @@
             "source_path": "aspnetcore/migration/identity.md",
             "redirect_url": "/aspnet/core/migration/fx-to-core/examples/identity",
             "redirect_document_id": false
+        },
+        {
+            "source_path": "aspnetcore/blazor/progressive-web-app.md",
+            "redirect_url": "/aspnet/core/blazor/progressive-web-app/",
+            "redirect_document_id": false
         }
     ]
 }

aspnetcore/blazor/components/css-isolation.md

@@ -58,26 +58,26 @@ CSS isolation occurs at build time. Blazor rewrites CSS selectors to match marku
 Blazor Web Apps:
 
 ```html
-<link href="@Assets["{ASSEMBLY NAME}.styles.css"]" rel="stylesheet">
+<link href="@Assets["{PACKAGE ID/ASSEMBLY NAME}.styles.css"]" rel="stylesheet">
 ```
 
 Standalone Blazor WebAssembly apps:
 
 ```html
-<link href="{ASSEMBLY NAME}.styles.css" rel="stylesheet">
+<link href="{PACKAGE ID/ASSEMBLY NAME}.styles.css" rel="stylesheet">
 ```
 
 :::moniker-end
 
 :::moniker range="< aspnetcore-9.0"
 
 ```html
-<link href="{ASSEMBLY NAME}.styles.css" rel="stylesheet">
+<link href="{PACKAGE ID/ASSEMBLY NAME}.styles.css" rel="stylesheet">
 ```
 
 :::moniker-end
 
-The `{ASSEMBLY NAME}` placeholder is the project's assembly name.
+The `{PACKAGE ID/ASSEMBLY NAME}` placeholder is the project's package ID (`<PackageId>` in the project file) for a library or assembly name for an app.
 
 :::moniker range="< aspnetcore-8.0"
 
@@ -95,7 +95,7 @@ Within the bundled file, each component is associated with a scope identifier. F
 <h1 b-3xxtam6d07>
 ```
 
-The `{ASSEMBLY NAME}.styles.css` file uses the scope identifier to group a style declaration with its component. The following example provides the style for the preceding `<h1>` element:
+The `{PACKAGE ID/ASSEMBLY NAME}.styles.css` file uses the scope identifier to group a style declaration with its component. The following example provides the style for the preceding `<h1>` element:
 
 ```css
 /* /Components/Pages/Counter.razor.rz.scp.css */
@@ -104,11 +104,11 @@ h1[b-3xxtam6d07] {
 }
 ```
 
-At build time, a project bundle is created with the convention `obj/{CONFIGURATION}/{TARGET FRAMEWORK}/scopedcss/projectbundle/{ASSEMBLY NAME}.bundle.scp.css`, where the placeholders are:
+At build time, a project bundle is created with the convention `obj/{CONFIGURATION}/{TARGET FRAMEWORK}/scopedcss/projectbundle/{PACKAGE ID/ASSEMBLY NAME}.bundle.scp.css`, where the placeholders are:
 
 * `{CONFIGURATION}`: The app's build configuration (for example, `Debug`, `Release`).
 * `{TARGET FRAMEWORK}`: The target framework (for example, `net6.0`).
-* `{ASSEMBLY NAME}`: The app's assembly name (for example, `BlazorSample`).
+* `{PACKAGE ID/ASSEMBLY NAME}`: The project's package ID (`<PackageId>` in the project file) for a library or assembly name for an app (for example, `BlazorSample`).
 
 ## Child component support
 

aspnetcore/blazor/fundamentals/configuration.md

@@ -300,12 +300,12 @@ var hostname = builder.Configuration["HostName"];
 
 ## Cached configuration
 
-Configuration files are cached for offline use. With [Progressive Web Applications (PWAs)](xref:blazor/progressive-web-app), you can only update configuration files when creating a new deployment. Editing configuration files between deployments has no effect because:
+Configuration files are cached for offline use. With [Progressive Web Applications (PWAs)](xref:blazor/progressive-web-app/index), you can only update configuration files when creating a new deployment. Editing configuration files between deployments has no effect because:
 
 * Users have cached versions of the files that they continue to use.
 * The PWA's `service-worker.js` and `service-worker-assets.js` files must be rebuilt on compilation, which signal to the app on the user's next online visit that the app has been redeployed.
 
-For more information on how background updates are handled by PWAs, see <xref:blazor/progressive-web-app#background-updates>.
+For more information on how background updates are handled by PWAs, see <xref:blazor/progressive-web-app/index#background-updates>.
 
 ## Options configuration