-
Notifications
You must be signed in to change notification settings - Fork 649
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
Rationale for dropping netstandard2.0 support? #6438
Comments
NServiceBus 8 will be targeting |
Well, yes - I do believe that we have one or two legacy systems running We are moving to Another aspect is the impact of our private, downstream NuGet packages that bundles NServiceBus with application specific customization. These packages can no longer target It feels like a big change in NServiceBus, and I'm surprised that there are no announcements or even clues in issues/PRs as to why this change is made. |
You're right, it is a big change. That's why it's a major version, because removing target frameworks is a breaking change. NServiceBus 8 is also still in beta, so a lot of the communication just hasn't happened yet. But here are some important things to keep in mind:
If you have private packages that bundle NServiceBus, then you will definitely need a new version of that to support NServiceBus 8, regardless of target framework. A package like that could target either |
My apologies for a late reply. Thanks for a detailed answer. It was something like this that I expected to find in the documentation but didn't (at the time the question was asked, at least 😅). Closing this issue. |
Looking forward to the next major version of
NServiceBus
. I was surprised to see that you are dropping support fornetstandard2.0
- what is the rational for this? It looks like the change was introduced in this commit 6454809. It was merged #5913 but introduced in (closed) PR #5890.The text was updated successfully, but these errors were encountered: