Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Allow configuration Azure:SignalR:Enabled false to disable Azure SignalR

See original GitHub issue

Describe the bug

For netcore31, instead of manually call AddAzureSignalR, you can enable or disable Azure SignalR through config:

{
  "Azure": {
    "SignalR": {
      "Enabled": false
    }
  }
}

However, once AddAzureSignalR is added to code, this configuration never works again, it does not sound a consistent behavior from the user’s perspective.

Issue Analytics

State:
Created 3 years ago
Reactions:2
Comments:8 (3 by maintainers)

Top GitHub Comments

1reaction

sodabluecommented, Sep 14, 2021

I think it would fundamentally make sense to have an Azure:SignalR:Enabled configuration item that would work even if you have AddAzureSignalR(). The documentation pretty clearly indicates for local dev we should bypass this, but offers no way to do this, absent writing our own conditional configuration code. I tried omiting the connection string, and it throws an exception. Then I found this article and tried the HostingStartupAssemblies setup, but in .net 5 this apparently either does not work or there’s more to it then this.

Even if it did work, I think the hostingstartupassemblies way of configuring this is incredibly obtuse and would make it very difficult for developers supporting the app to understand what is happening.

1reaction

crackalakcommented, Mar 5, 2021

I was suprised when this didn’t work, can this be fixed please? 😃