Allow serialization of invalid xml characters #766
Merged
Conversation
This file contains 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
…nnot be modified. Check if response.HasStarted, to avoid hiding of serialization exception
Full framework soap service allows serialization of invalid utf-8 characters so I thing soapcore should too
|
If you merge this PR I'd appreciate a new nuget package |
Merged
andersjonsson
deleted the
allow-serialization-of-invalid-xml-characters
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Full framework Web Service allows weird control characters etc. in the xml output but XmlTextWriter doesn't by default.
Added Option "CheckXmlCharacters" (default true) to give control over CheckCharacters-property on XmlTextWriter