Skip to content

Commit

Permalink
Reword SerializationBinder note per suggestion
Browse files Browse the repository at this point in the history
Co-authored-by: Immo Landwerth <[email protected]>
  • Loading branch information
jeffhandley and terrajobst authored Aug 7, 2024
1 parent c874cb2 commit b129893
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -86,4 +86,4 @@ It's recommended to use [SerializationBinder](/dotnet/api/system.runtime.seriali

Using this type requires inheriting from it and overriding the [Type BindToType(string assemblyName, string typeName)](/dotnet/api/system.runtime.serialization.serializationbinder.bindtotype#system-runtime-serialization-serializationbinder-bindtotype(system-string-system-string)) method.

If your code uses a custom type that derives from `SerializationBinder`, it's likely that the list of serializable types is a **closed set**. If not, finding the list of all types that can get serialized and deserialized requires studying all the usages of `BinaryFormatter` in source code. **Knowing that list is crucial to determining how to move forward with the migration.**
Ideally the list of serializable types is closed set because it means you know which types can be instantiated which will help reduce security vulnerabilities.

Check failure on line 89 in docs/standard/serialization/binaryformatter-migration-guide/functionality-reference.md

View workflow job for this annotation

GitHub Actions / lint

Trailing spaces

docs/standard/serialization/binaryformatter-migration-guide/functionality-reference.md:89:160 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1] https://github.com/DavidAnson/markdownlint/blob/v0.34.0/doc/md009.md

0 comments on commit b129893

Please sign in to comment.