Roadmap for SignalR-Client-Cpp project

[mprather]

The SignalR-Client-Cpp project has seen very little traction in the past 2 years. PR's have been ignored and issues have been somewhat stagnant.

Project owners like myself and others are wondering what is going to happen (see #59665).

Our projects go through a normal update process with vcpkg. I was shocked to see the microsoft-signalr was removed in the last monthly release 2025.03.19. Per the comments in microsoft/vcpkg#42678 (comment), a fellow softie has stated that signalr is either dead or deprecated.

The removal of microsoft-signalr from vcpkg is a back breaker. We use other dependencies that are cleanly and effectively managed by vcpkg. If the de-indexing of the signalr package is in fact a true reflection of the stance of the project team, then it would really help the community for the signalr c++ team to announce they are in fact pulling all support.

Then project owners can take the appropriate steps to move off signalr. Otherwise, everyone is left in a weird holding pattern where the latest release is still listed as an alpha and code is barely plodding along.

Please help the c++ community by providing clear guidance on library.

[BrennanConroy]

I was shocked to see the microsoft-signalr was removed in the last monthly release 2025.03.19.

This was unexpected, we're reaching out to the vcpkg team and will try to resolve this.

The SignalR-Client-Cpp project has seen very little traction in the past 2 years. PR's have been ignored and issues have been somewhat stagnant.

Project owners like myself and others are wondering what is going to happen (see #59665).

I'll reply on that issue, answer is effectively that the library has been and still is in alpha mode and will stay in alpha for the foreseeable future. We aren't able to put many resources into making it a beta or GA product right now.