Remove BinaryFormatter support from Control's ActiveX projection. #7986
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
In order for properties to be exposed to `IPropertyBag` they must have a TypeConverter to and from either string (preferred) or `byte[]`. These were always the first choice, ISerializable was the final fallback. This matches what we've done elsewhere when we've removed BinaryFormatter.
lonitra
approved these changes
Oct 21, 2022
|
There will be a follow up change to deal with the |
ghost
locked as resolved and limited conversation to collaborators
JeremyKuhne
added
the
area-Serialization-BinaryFormatter-FeatureWork
|
I put this back with #8597 as I mistakenly thought the plan was to completely remove the |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In order for properties to be exposed to
IPropertyBagthey must have a TypeConverter to and from either string (preferred) orbyte[].These were always the first choice,
ISerializablewas the final fallback. This matches what we've done elsewhere when we've removedBinaryFormatter.cc: @GrabYourPitchforks, @merriemcgaw
Microsoft Reviewers: Open in CodeFlow