Epic- Update BinaryFormatter usage

[merriemcgaw]

Official BinaryFormatter removal announcement: dotnet/runtime#98245

BinaryFormatter is an inherently unsafe serliazer. WinForms used it quite a bit in early versions and now we should remove as much of this as possible.

This is part of the dotnet/planning/issues/27 theme

• Consider aggressive AppContext switch for enabling safer BinaryFormatedObject usage #8290
• Investigate adding additional TypeConverter metadata to Resx #8297
• Add test coverage for ResX classes #8295
• Clean up usage of BinaryFormatter throughout codebase #1251
• Document how to add a custom TypeConverter for AxHost.State serialization #8296
• Remove BinaryFormatter for property bag serialization #7988
• Remove BinaryFormatter support from Control's ActiveX projection. #7986
• CSV format is put on clipboard as BinaryFormatted string #9059
• Public WinForms / .NET types require the BinaryFormatter when serializing public properties. #9110
• Look at limiting BinaryFormatter usage with CodeDomSerializationStore #9428

Related:

• Epic - Improve Clipboard functionality #6269
• Epic - Make WinForms trim compatible #4649

[weltkante]

whats the replacement for BinaryFormatter in clipboard/drag'n'drop data exchange? anything been announced yet?

[edit] found it myself, #6269, sorry for the noise, will follow that issue as it evolves.

[RussKie]

At this stage we don't have any formed plans or announcements. Binary formatters are used in multiple scenarios - e.g. the clipboard and resources. We are fully aware this deprecation will likely have far reaching impact, and we need to plan accordingly.