Remove subscription versioning for MSMQ and InMemory subscriptions #4177
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Symptoms
Subscribers no longer receive events published if the publisher changes the
Major
assembly version part on the contract assembly without subscribers being updated at the same time.Who's affected
All users on a transport using message driven pub/sub that have a message contract versioning strategy that increases the
Major
assembly version part for changes that are not to be considered breaking for subscribers.