Master tracking issue for removing BinaryFormatter usage from dotnet libs #39287
Description
This issue tracks the tagging and removal of BinaryFormatter-related code paths from various dotnet org repos. See dotnet/designs#141 for more information.
dotnet/runtime
- Obsolete SerializationFormat.Binary in DataTable/DataSet and put it behind an appcontext switch #39289 - usage in
DataSet - Remove BinaryFormatter usage from ResourceReader #39290 - usage in
ResourceReader - Remove BinaryFormatter usage from System.Resources.Extensions #39292 - usage in System.Resources.Extensions
- Remove BinaryFormatter usage from System.ComponentModel.TypeConverter #39293 - usage in System.ComponentModel.TypeConverter (Prohibit BF unless the app opts in #48527)
- Remove BinaryFormatter usage from SettingsPropertyValue #39295 - usage in System.Configuration.ConfigurationManager (BinaryFormatter deprecation for System.Configuration.ConfigurationManager #50531)
- Consider allowing Exception instances to be serialized without requiring BinaryFormatter #43482 - Exception serialization without BinaryFormatter
Documentation of Breaking Changes
As part of the definition of done for each of these items, we must identify possibilities where changing serialization formats could be a breaking change for customers. For instance, if the serialized output could have been persisted to disk, we will likely need to document where the deserialization of persisted data could be affected.