Improve placeholders for libraries (#35686)

Author: guardrex

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/startup.md

@@ -205,7 +205,7 @@ Both callbacks can return a `Promise`, and the promise is awaited before the sta
 For the file name:
 
 * If the JS initializers are consumed as a static asset in the project, use the format `{ASSEMBLY NAME}.lib.module.js`, where the `{ASSEMBLY NAME}` placeholder is the app's assembly name. For example, name the file `BlazorSample.lib.module.js` for a project with an assembly name of `BlazorSample`. Place the file in the app's `wwwroot` folder.
-* If the JS initializers are consumed from an RCL, use the format `{LIBRARY NAME/PACKAGE ID}.lib.module.js`, where the `{LIBRARY NAME/PACKAGE ID}` placeholder is the project's library name or package identifier. For example, name the file `RazorClassLibrary1.lib.module.js` for an RCL with a package identifier of `RazorClassLibrary1`. Place the file in the library's `wwwroot` folder.
+* If the JS initializers are consumed from an RCL, use the format `{LIBRARY NAME/PACKAGE ID}.lib.module.js`, where the `{LIBRARY NAME/PACKAGE ID}` placeholder is the project's library name or package identifier (`<PackageId>` value in the library's project file). For example, name the file `RazorClassLibrary1.lib.module.js` for an RCL with a package identifier of `RazorClassLibrary1`. Place the file in the library's `wwwroot` folder.
 
 :::moniker-end
 

aspnetcore/blazor/javascript-interoperability/call-dotnet-from-javascript.md

@@ -33,12 +33,12 @@ Pass in the name of the assembly containing the method, the identifier of the st
 
 In the following example:
 
-* The `{ASSEMBLY NAME}` placeholder is the app'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.
 * The `{.NET METHOD ID}` placeholder is the .NET method identifier.
 * The `{ARGUMENTS}` placeholder are optional, comma-separated arguments to pass to the method, each of which must be JSON-serializable.
 
 ```javascript
-DotNet.invokeMethodAsync('{ASSEMBLY NAME}', '{.NET METHOD ID}', {ARGUMENTS});
+DotNet.invokeMethodAsync('{PACKAGE ID/ASSEMBLY NAME}', '{.NET METHOD ID}', {ARGUMENTS});
 ```
 
 `DotNet.invokeMethodAsync` returns a [JS `Promise`](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Promise) representing the result of the operation. `DotNet.invokeMethod` (client-side components) returns the result of the operation.
@@ -239,7 +239,7 @@ In the call to `DotNet.invokeMethodAsync` (server-side or client-side components
 Call `DotNet.createJSObjectReference(jsObject)` to construct a JS object reference so that it can be passed to .NET, where `jsObject` is the [JS `Object`](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Object) used to create the JS object reference. The following example passes a reference to the non-serializable `window` object to .NET, which receives it in the `ReceiveWindowObject` C# method as an <xref:Microsoft.JSInterop.IJSObjectReference>:
 
 ```javascript
-DotNet.invokeMethodAsync('{ASSEMBLY NAME}', 'ReceiveWindowObject', 
+DotNet.invokeMethodAsync('{PACKAGE ID/ASSEMBLY NAME}', 'ReceiveWindowObject', 
   DotNet.createJSObjectReference(window));
 ```
 
@@ -251,7 +251,7 @@ public static void ReceiveWindowObject(IJSObjectReference objRef)
 }
 ```
 
-In the preceding example, the `{ASSEMBLY NAME}` placeholder is the app's namespace.
+In the preceding example, 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.
 
 > [!NOTE]
 > The preceding example doesn't require disposal of the `JSObjectReference`, as a reference to the `window` object isn't held in JS.
@@ -261,12 +261,12 @@ Maintaining a reference to a `JSObjectReference` requires disposing of it to avo
 ```javascript
 var jsObjectReference = DotNet.createJSObjectReference(window);
 
-DotNet.invokeMethodAsync('{ASSEMBLY NAME}', 'ReceiveWindowObject', jsObjectReference);
+DotNet.invokeMethodAsync('{PACKAGE ID/ASSEMBLY NAME}', 'ReceiveWindowObject', jsObjectReference);
 
 DotNet.disposeJSObjectReference(jsObjectReference);
 ```
 
-In the preceding example, the `{ASSEMBLY NAME}` placeholder is the app's namespace.
+In the preceding example, 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.
 
 Call `DotNet.createJSStreamReference(streamReference)` to construct a JS stream reference so that it can be passed to .NET, where `streamReference` is an [`ArrayBuffer`](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer), [`Blob`](https://developer.mozilla.org/docs/Web/API/Blob), or any [typed array](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/TypedArray), such as [`Uint8Array`](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Uint8Array) or [`Float32Array`](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Float32Array), used to create the JS stream reference.
 

aspnetcore/blazor/security/webassembly/additional-scenarios.md

@@ -410,7 +410,7 @@ A typed client can be defined that handles all of the HTTP and token acquisition
 ```csharp
 using System.Net.Http.Json;
 using Microsoft.AspNetCore.Components.WebAssembly.Authentication;
-using static {ASSEMBLY NAME}.Data;
+using static {PACKAGE ID/ASSEMBLY NAME}.Data;
 
 public class WeatherForecastClient(HttpClient http)
 {
@@ -433,7 +433,7 @@ public class WeatherForecastClient(HttpClient http)
 }
 ```
 
-In the preceding example, the `WeatherForecast` type is a static class that holds weather forecast data. The `{ASSEMBLY NAME}` placeholder is the app's assembly name (for example, `using static BlazorSample.Data;`).
+In the preceding example, the `WeatherForecast` type is a static class that holds weather forecast data. 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 (for example, `using static BlazorSample.Data;`).
 
 In the following example, <xref:Microsoft.Extensions.DependencyInjection.HttpClientFactoryServiceCollectionExtensions.AddHttpClient%2A?displayProperty=nameWithType> is an extension in <xref:Microsoft.Extensions.Http?displayProperty=fullName>. Add the package to an app that doesn't already reference it.