Support configuring ILBasedSerializer and BinaryFormatterISerializableSerializer as pre-fallback serializers #7384
+36
−7
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
…eSerializer as pre-fallback serializers
ReubenBond
force-pushed
the
v3/support-non-fallback-keyed-serializers
branch
from
ab76997 to
1d029a1
Compare
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.
This allows a developer to configure
ILBasedSerializerOptionsorBinaryFormatterISerializableSerializerOptionsand set their respectiveIsFallbackOnlyproperties tofalseto revert serializer behavior to pre-3.5.0.The optimum solution if you are considering this is to add
[Serializable]to your types and ensure that the code generator is generating code for your types, but this PR gives you an alternative route.Microsoft Reviewers: Open in CodeFlow