Add more warnings about BinaryFormatter and NetDataContractSerializer #43433
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
jeffhandley
requested review from
a team,
BillWagner,
IEvangelist and
gewarren
as code owners
gewarren
approved these changes
Nov 12, 2024
docs/standard/serialization/binaryformatter-migration-guide/choose-a-serializer.md
Outdated
Show resolved
Hide resolved
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.
I searched through all references to BinaryFormatter and found a few places where we could use more warnings about its dangers. There were also a couple places where warnings about
NetDataContractSerializerseemed prudent.For the Orleans doc change, please note it's in the 3.x pivot on the page and not visible on the 7.0 pivot.
This was prompted by Don't recommend BinaryFormatter (dotnet/docs-desktop#1551).
Internal previews