Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[3.0.0] Breaking Change Tracking #5312

Closed
1 of 3 tasks
analogrelay opened this issue Jun 29, 2018 · 8 comments
Closed
1 of 3 tasks

[3.0.0] Breaking Change Tracking #5312

analogrelay opened this issue Jun 29, 2018 · 8 comments
Labels
area-signalr Includes: SignalR clients and servers
Milestone
3.0.0

Comments

@analogrelay
Copy link
Contributor

analogrelay commented Jun 29, 2018 •
edited
Loading

This issue is to track breaking changes implemented or planned for 3.0 to ensure they get announced properly
@analogrelay analogrelay changed the title Breaking Change Tracking [3.0.0] Breaking Change Tracking Jun 29, 2018
@analogrelay
Copy link
Contributor Author

analogrelay commented Nov 19, 2018 •
edited
Loading

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 IHubProtocol, since that's a breaking change... @davidfowl @BrennanConroy @mikaelm12 @bradygaster

@aspnet-hello aspnet-hello transferred this issue from aspnet/SignalR Dec 17, 2018
@aspnet-hello aspnet-hello added this to the 3.0.0 milestone Dec 17, 2018
@aspnet-hello aspnet-hello added area-signalr Includes: SignalR clients and servers cost: 0 labels Dec 17, 2018
@Eilon
Copy link
Member

Eilon commented Apr 19, 2019 •
edited
Loading

@anurse - is this a PRI-0 bug, and is it in the correct milestone?

@analogrelay
Copy link
Contributor Author

This isn't really used anymore.

@MagicAndre1981
Copy link

@anurse

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?

@MagicAndre1981
Copy link

@anurse

ok, I found this link

Is this all?

@analogrelay
Copy link
Contributor Author

analogrelay commented Sep 24, 2019 •
edited
Loading

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).

@MagicAndre1981
Copy link

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.

@analogrelay
Copy link
Contributor Author

I'd suggest you watch aspnet/Announcements as that's where announcements like this would be posted.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-signalr Includes: SignalR clients and servers
Projects
None yet
Milestone
3.0.0
Development

No branches or pull requests
4 participants
@analogrelay @Eilon @MagicAndre1981 @aspnet-hello