Skip to content
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.

Sign up for GitHub

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

Jump to bottom

We need to understand the plan for deprecation of BinaryFormatter #6858

Closed
jjmew opened this issue Jan 23, 2021 · 1 comment
Closed

We need to understand the plan for deprecation of BinaryFormatter #6858

jjmew opened this issue Jan 23, 2021 · 1 comment
Assignees
@MiYanni
Labels
Triage-Approved Reviewed and prioritized
Milestone
16.10

Comments

@jjmew
Copy link
Contributor

jjmew commented Jan 23, 2021

We need to understand the plan for deprecation of BinaryFormatter. We use it for the Resource Designer but we need to move to a new solution as it will be deprecated. You can see dotnet/runtime#39292
@jjmew jjmew added the Triage-Approved Reviewed and prioritized label Jan 26, 2021
@jjmew jjmew added this to the 16.10 milestone Jan 26, 2021
@MiYanni MiYanni mentioned this issue Feb 17, 2021
Merged
@MiYanni
Copy link
Member

MiYanni commented Jun 2, 2021

Current plan is to replace BinaryFormatter usage. It is used for undo/redo of the old property pages and used for drag & drop/copy-paste in the resource designer. I'm currently working on a solution using System.Text.Json.

@MiYanni MiYanni closed this as completed Jun 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MiYanni MiYanni

Labels
Triage-Approved Reviewed and prioritized
Projects
None yet
Milestone
16.10
Development

No branches or pull requests
2 participants
@jjmew @MiYanni