Merge pull request #7752 from Particular/hosting-extensions

Review hosting extension

Author: WilliamBZA

nservicebus/hosting/extensions-hosting.md

@@ -2,55 +2,55 @@
 title: NServiceBus.Extensions.Hosting
 summary: NServiceBus integration with Microsoft.Extensions.Hosting
 component: Extensions.Hosting
-reviewed: 2023-11-23
+reviewed: 2025-08-19
 related:
  - samples/hosting/generic-host
  - samples/dependency-injection/aspnetcore
 ---
 
 ## Configuration
 
-An NServiceBus endpoint can be hosted within the generic host with the `UseNServiceBus` extension method:
+An NServiceBus endpoint can be hosted in the .NET Generic Host using the `UseNServiceBus` extension method:
 
 snippet: extensions-host-configuration
 
-This code will register the endpoint with the hosting infrastructure and automatically start and stop it based on the host's application lifetime.
+This registers the endpoint with the hosting infrastructure and starts/stops it automatically with the application's lifetime.
 
 > [!WARNING]
-> Specify `UseNServiceBus` before any other service (e.g. `ConfigureWebHostDefaults`) which requires access to the `IMessageSession`. Incorrect usage results in a `System.InvalidOperationException` with the following message:
+> Call `UseNServiceBus` **before** registering any component that needs `IMessageSession`. Placing it later can cause a `System.InvalidOperationException`:
+>
 > > The message session can't be used before NServiceBus is started. Place `UseNServiceBus()` on the host builder before registering any hosted service (e.g. `services.AddHostedService<HostedServiceAccessingTheSession>()`) or the web host configuration (e.g. `builder.ConfigureWebHostDefaults`) if hosted services or controllers require access to the session.
 
 ## Logging integration
 
-NServiceBus logging is automatically configured to use the [logging configured](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/logging) for the [generic host](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/host/generic-host); no NServiceBus specific logging configuration is needed.
+NServiceBus logging is automatically wired to the host's logging pipeline. No NServiceBus-specific logging configuration is required. See [.NET logging](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/logging) and the [Generic Host](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/host/generic-host).
 
 > [!WARNING]
-> [NServiceBus.Extensions.Logging](/nservicebus/logging/extensions-logging.md) or [NServiceBus.MicrosoftLogging.Hosting](https://www.nuget.org/packages/NServiceBus.MicrosoftLogging.Hosting) should not be used.
+> Do **not** use [NServiceBus.Extensions.Logging](/nservicebus/logging/extensions-logging.md) or [NServiceBus.MicrosoftLogging.Hosting](https://www.nuget.org/packages/NServiceBus.MicrosoftLogging.Hosting) with `NServiceBus.Extensions.Hosting`.
 
 ## Dependency injection integration
 
-NServiceBus endpoints hosted as part of the generic host automatically use the provided `IServiceCollection` and `IServiceProvider` dependency injection infrastructure. Message handlers can resolve dependencies which are registered in the `IServiceCollection`.
+When hosted in the Generic Host, NServiceBus uses the application's `IServiceCollection` / `IServiceProvider`. Message handlers can resolve services registered in `IServiceCollection`.
 
-`UseNServiceBus` automatically registers an `IMessageSession` with the container which can be resolved from the `IServiceProvider` or via dependency injection during runtime.
+`UseNServiceBus` also registers an `IMessageSession` that can be resolved from the container or injected where needed at runtime.
 
 ### Configure custom containers
 
-Custom dependency injection containers may be configured using `IWebHostBuilder.UseServiceProviderFactory`. NServiceBus automatically uses the host's dependency injection container. Refer to the container's documentation for further details.
+To use a third-party container, configure it with `HostBuilder.UseServiceProviderFactory(...)`. NServiceBus will automatically use the host’s container. Refer to your container’s documentation for details.
 
 partial: shutdown-timeout
 
 ## Stopping the endpoint
 
-When using the generic host, the `IEndpointInstance` interface to stop the endpoint is not directly exposed. To stop the endpoint, use the [`IApplicationLifetime`](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.hosting.ihostapplicationlifetime) interface to gracefully stop the NServiceBus endpoint and other hosted services. See the [generic host application lifetime documentation](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/host/generic-host#ihostapplicationlifetime) for further information.
+With the Generic Host, the `IEndpointInstance` used to stop the endpoint is not exposed directly. To shut down gracefully, request application shutdown via [`IHostApplicationLifetime`](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.hosting.ihostapplicationlifetime). See [Generic Host application lifetime](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/host/generic-host#ihostapplicationlifetime) for more information.
 
 ## Installers
 
-It is not recommended to always run the [NServiceBus installers](/nservicebus/operations/installers.md) by invoking `.EnableInstallers()` as this delays startup time and might require more permissions.
+Avoid always running [NServiceBus installers](/nservicebus/operations/installers.md) via `.EnableInstallers()` as it adds startup time and may require elevated permissions.
 
-Instead of invoking `host.`
+Instead, run installers explicitly in a dedicated “setup” mode:
 
-Example:
-```c#
+```csharp
 var isSetup = args.Contains("-s") || args.Contains("/s");
 
 if (isSetup)
@@ -65,5 +65,3 @@ if (isSetup)
 
 // Continue and eventually invoke:
 // await host.RunAsync();
-```
-