A service client for Azure Web PubSub that integrates with Aspire, including health checks, logging and telemetry.
$ dotnet add package Aspire.Azure.Messaging.WebPubSubRegisters a WebPubSubServiceClient in the DI container for connecting to Azure Web PubSub.
Install the Aspire Azure Web PubSub library with NuGet:
dotnet add package Aspire.Azure.Messaging.WebPubSub
In the AppHost.cs file of your project, call the AddAzureWebPubSubHub extension method to register a WebPubSubServiceClient for use via the dependency injection container. The method takes a connection name parameter.
builder.AddAzureWebPubSubServiceClient("wps1");
You can then retrieve the WebPubSubServiceClient instance using dependency injection. For example, to retrieve the client from a Web API controller:
private readonly WebPubSubServiceClient _client;
public ProductsController(WebPubSubServiceClient client)
{
_client = client;
}
See the Azure.Messaging.WebPubSub documentation for examples on using the WebPubSubServiceClient.
The Aspire Azure Web PubSub library provides multiple options to configure the Azure Web PubSub connection based on the requirements and conventions of your project. Note that either a Endpoint or a ConnectionString is a required to be supplied.
When using a connection string from the ConnectionStrings configuration section, you can provide the name of the connection string when calling builder.AddAzureWebPubSubHub():
builder.AddAzureWebPubSubServiceClient("WebPubSubConnectionName", "your_hub_name");
And then the connection information will be retrieved from the ConnectionStrings configuration section. Two connection formats are supported:
The recommended approach is to use the service endpoint, which works with the AzureMessagingWebPubSubSettings.Credential property to establish a connection. If no credential is configured, the DefaultAzureCredential is used.
{
"ConnectionStrings": {
"WebPubSubConnectionName": "https://xxx.webpubsub.azure.com"
}
}
Alternatively, a connection string can be used.
{
"ConnectionStrings": {
"WebPubSubConnectionName": "Endpoint=https://xxx.webpubsub.azure.com;AccessKey==xxxxxxx"
}
}
The Aspire Azure Web PubSub library supports Microsoft.Extensions.Configuration. It loads the AzureMessagingWebPubSubSettings and WebPubSubServiceClientOptions from configuration by using the Aspire:Azure:Messaging:WebPubSub key. Example appsettings.json that configures some of the options:
{
"Aspire": {
"Azure": {
"Messaging": {
"WebPubSub": {
"DisableHealthChecks": true,
"HubName": "your_hub_name"
}
}
}
}
}
You can also pass the Action<AzureMessagingWebPubSubSettings> configureSettings delegate to set up some or all the options inline, for example to disable health checks from code:
builder.AddAzureWebPubSubServiceClient("wps", settings => settings.DisableHealthChecks = true);
You can also setup the WebPubSubServiceClientOptions using the optional Action<IAzureClientBuilder<WebPubSubServiceClient, WebPubSubServiceClientOptions>> configureClientBuilder parameter of the AddAzureWebPubSubHub method. For example, to set the client ID for this client:
builder.AddAzureWebPubSubServiceClient("wps", configureClientBuilder: clientBuilder => clientBuilder.ConfigureOptions(options => options.Retry.MaxRetries = 5));
In your AppHost project, add a Web PubSub connection and consume the connection using the following methods:
var webPubSub = builder.AddAzureWebPubSub("wps");
var myService = builder.AddProject<Projects.MyService>()
.WithReference(webPubSub);
The AddAzureWebPubSubHub method will read connection information from the AppHost's configuration (for example, from "user secrets") under the ConnectionStrings:wps config key. The WithReference method passes that connection information into a connection string named wps in the MyService project. In the Program.cs file of MyService, the connection can be consumed using:
builder.AddAzureWebPubSubServiceClient("wps");