-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove BinaryFormatter uses #1131
Comments
Note that this will break drag'n'drop and clipboard comatibility with desktop framework applications for nontrivial content, unless the replacement is able to produce/consume the same binary data. |
Looks like this ended up getting punted to the .NET 7 timeline. We're now in .NET 8, though, and this is causing crashes in some applications that rely on WPF (see picoe/Eto#2607). Is there a plan to address this issue beyond just telling applications to use an insecure serializer? |
As far as I'm aware WinForms hasn't switched away from BinaryFormatter clipboard/drag'n'drop usage either, they seem to have pushed it to .NET 9 issue search link. So no, at the moment there is nothing, I would expect WinForms to make this step before WPF since they are usually more active. Its unfortunate that the core/runtime guys are overly eager to warn (and possibly break) people before things are ready. |
Thanks for the reply @weltkante. That makes sense -- for now I suppose we'll just have to disable that break until at least .NET 9. Appreciate the help! |
FYI: Deadline has been set dotnet/runtime#98245 |
Related:
https://github.com/dotnet/corefx/issues/38760
BinaryFormatter
will be removed in .NET 5. Remove its uses with whatever drop-in replacement is provided in .NET 5.The text was updated successfully, but these errors were encountered: