Fix support for MessageVersion.Soap12#1178
Merged
Merged
Conversation
Collaborator
|
Thank you! |
This was referenced Jun 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
MessageVersion.Soap12was introduced (or to be more precise, the missing API has been added) withSystem.ServiceModel.Primitivesversion 6.1.0: dotnet/wcf@7b01263For this reason, the comparison with this SOAP version was probably missing in the code, because this cannot be called with the version of .NET Core 3.1.
I have replaced the comparison to the concrete
MessageVersionwith theEnvelopeVersionin the code passages, because this is actually the point of interest.I had noticed this, because when calling the
...?wsdlURL the error “Unsupported MessageVersion encountered while writing envelope.” was thrown.