-
Notifications
You must be signed in to change notification settings - Fork 9.9k
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
[3.0.0] Breaking Change Tracking #5312
Comments
P0 so we see it often. This was just tracking the things we need to announce as part of breaking changes. Now that active 3.0 development is starting, we can probably just announce the things as they come up. On a side note: We need to talk about the addition of the MinorVersion property to |
@anurse - is this a PRI-0 bug, and is it in the correct milestone? |
This isn't really used anymore. |
where is a documentation for breaking changes in 3.0 final? The SignalR page was not updated since 2018 and misses a migration guide from 2.2 to 3.0. What steps do I have to follow to upgrade from 2.2 to 3.0? What is changed/removed? I only know my selfhost must be now .net core 3.0 app. What else is changed? |
Yes, that is the migration guide for SignalR. It may not be a complete breaking change list, but it covers most of the core scenarios. A full list of breaking changes in ASP.NET Core can be found in the issue tracker for aspnet/Announcements (and you can subscribe to that repo to get GitHub notifications when new breaking changes are introduced in 3.1 and beyond). Moving forward, we are also working on publishing ASP.NET Core breaking changes to the central .NET Core Breaking Changes page on our documentation site (but we haven't completed that yet). |
ok, please also reply here when the link goes online. |
I'd suggest you watch aspnet/Announcements as that's where announcements like this would be posted. |
This issue is to track breaking changes implemented or planned for 3.0 to ensure they get announced properly
IHubProtocol
AddJsonProtocol
toAddNewtonsoftJsonProtocol
)The text was updated successfully, but these errors were encountered: