You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue has been transferred from the Azure SDK for .NET repository, #45140.
Please be aware that @kajusknoras is the author of the original issue and include them for any questions or replies.
Details
With the previous Azure SDK (WindowsAzure.ServiceBus) it was possible to do so. In a .NET Framework (4.8) application, whilst migrating to Azure.Messaging.ServiceBus, we've realized that support for scaling out for SignalR, that was originally achievable with GlobalHost.DependencyResolver.UseServiceBus(connectionString, topicPrefix) does not exist.
This is now missing or is not documented. Perhaps one of the alternatives could be that support for Microsoft.AspNet.SignalR.ServiceBus3 or Microsoft.AspNet.SignalR.ServiceBus is added with Azure.Messaging.ServiceBus?
The text was updated successfully, but these errors were encountered:
Issue Transfer
This issue has been transferred from the Azure SDK for .NET repository, #45140.
Please be aware that @kajusknoras is the author of the original issue and include them for any questions or replies.
Details
With the previous Azure SDK (WindowsAzure.ServiceBus) it was possible to do so. In a .NET Framework (4.8) application, whilst migrating to Azure.Messaging.ServiceBus, we've realized that support for scaling out for SignalR, that was originally achievable with
GlobalHost.DependencyResolver.UseServiceBus(connectionString, topicPrefix)does not exist.This is now missing or is not documented. Perhaps one of the alternatives could be that support for Microsoft.AspNet.SignalR.ServiceBus3 or Microsoft.AspNet.SignalR.ServiceBus is added with Azure.Messaging.ServiceBus?
The text was updated successfully, but these errors were encountered: