-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Reword SerializationBinder note per suggestion
Co-authored-by: Immo Landwerth <[email protected]>
- Loading branch information
1 parent
c874cb2
commit b129893
Showing
1 changed file
with
1 addition
and
1 deletion.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -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 GitHub Actions / lintTrailing spaces
|