-
Notifications
You must be signed in to change notification settings - Fork 10k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Trimming] SignalR #41704
Comments
Thanks for contacting us. We're moving this issue to the |
Thanks for contacting us. We're moving this issue to the |
Hey there! |
.NET ships yearly. We just finished 8, so 9 is next year. This will be considered in planning (which we haven’t done yet) |
Thank you for your answer @davidfowl. I guess this won't weight much, but if it could get prioritized that'll be awesome. There isn't any solid alternative to SignalR, and this NativeAOT compatiblity is our single blocker as of today. |
You can use raw WebSockets as an alternative. NativeAOT incompatibility is going to everywhere 😄 that didn't plan for it. |
#56079 and #56460 make the core of SignalR client and server, along with the JsonProtocol trimming and AOT compatible with the following known limitations/drawbacks:
|
The core of SignalR server and client is trimming and native AOT compatible as of .NET 9 Preview 7. Along with the Json protocol. Leaving this issue open to track also making the following trim and native AOT compatible: |
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
SignalR should run in a trimmed app.
Describe the solution you'd like
Shipping projects under https://github.com/dotnet/aspnetcore/tree/main/src/SignalR need to add support for trimming.
See https://github.com/dotnet/aspnetcore/blob/main/docs/Trimming.md for instructions
Additional context
No response
The text was updated successfully, but these errors were encountered: