- Notifications
You must be signed in to change notification settings - Fork353
ThrowPlatformNotSupportedException
innetstandard1.3
#396
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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
- stop trying to use DCS in the JSON and XML formatters- if `UseDataContractSerializer` or `!UseXmlSerializer`: - `CanReadType(...)` and `CanWriteType(...)` always return `false` - `ReadFromStreamAsync(...)` and `WriteToStreamAsync(...)` always `throw`- change default XML formatter configuration to use `XmlSerializer`- adjust and disable tests in reaction- add tests of new `netstandard1.3` behavior- nits: - correct namespace of `SerializerConsistencyTests`; was alone in previous namespace - s/DataContractFormatter/XmlSerializerFormatter/ to reflect actual `XmlMediaTypeFormatter` test actions
/ping reviewers |
mconnew approved these changesMar 6, 2023
Thanks@mconnew. Unfortunately, it appears only a select few have write access in this repo 😦 That means I need another reviewer. |
wtgodbe approved these changesMar 6, 2023
dougbu added a commit that referenced this pull requestMar 7, 2023
* Use `msbuild` from VS 2022 if available - should ease local and TeamCity builds - make `%InstallDir%` unquoted (unlike `%vswhere%`) - shorten `%Path%` slightly - nits: - use script location more; no need to change directories* React to new build issues - follow up to#396 (unsure why new FxCop and "spelling" errors didn't fail that PR)* Put `PortReserver` users into an xUnit collection
Sign up for freeto 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.
UseDataContractSerializer
or!UseXmlSerializer
:CanReadType(...)
andCanWriteType(...)
always returnfalse
ReadFromStreamAsync(...)
andWriteToStreamAsync(...)
alwaysthrow
XmlSerializer
netstandard1.3
behaviorSerializerConsistencyTests
; was alone in previous namespaceXmlMediaTypeFormatter
test actions