microsoft / microsoft/aspire

SignalR client address resolution

Open
#1,356 16 comments 13 reactions 0 assignees View on GitHub
area-service-discovery documentation
Dominant language
C#
Stars
6.3k
Forks
991
Avg merge
2d 15h
Merged PRs (30d)
196

Description

Hello,

I am working on a project integrating SignalR with .NET Aspire and have encountered a specific challenge related to automatic address resolution for connections.

We are using SignalR Client for real-time communication, and currently, the configuration of the SignalR hub connection address is done manually in the appsettings.json.

Specific Challenge:
While in HttpClient, using a generic address like http://apiservice automatically resolves the correct address, this approach does not work with the SignalR client. When attempting to use http://apiservice or ws://apiservice with the SignalR client, the connection fails to establish, indicating an issue with automatic address resolution.

Is there a way to configure the SignalR client in .NET Aspire to automatically resolve the connection address, similar to what happens with HttpClient?
If so, what are the steps to implement this functionality, or where can I find relevant documentation?
I would greatly appreciate any guidance, suggestions, or code examples that could help resolve this issue. Thank you very much for your assistance!

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.