BinaryFormatter long-term obsoletion plan #141
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
This was referenced Jul 14, 2020
|
Never mind, this repo doesn't have milestones. |
|
@GrabYourPitchforks is there anything else we need to review? |
|
I need to go back through the video and see how far we got. If we got through the entire proposal then there's nothing left to review. |
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.
This document covers the winding down of
BinaryFormatterwithin .NET.Starting with .NET 5, we'll start obsoleting APIs and disabling
BinaryFormatter-related features in certain project types. Eventually all code within the dotnet repo is to be migrated fully off ofBinaryFormatter, at which point the implementation is to be removed from the runtime./cc @terrajobst