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

Port FxCop rule CA2240: ImplementISerializableCorrectly #551

Closed
Tracked by #61964
ghost opened this issue Nov 21, 2015 · 1 comment
Closed
Tracked by #61964

Port FxCop rule CA2240: ImplementISerializableCorrectly #551

ghost opened this issue Nov 21, 2015 · 1 comment
Labels
FxCop-Port Resolution-Won't Fix
Milestone
Unknown

Comments

@ghost
Copy link

ghost commented Nov 21, 2015

Title: Implement ISerializable correctly

Description:

To fix a violation of this rule, make the GetObjectData method visible and overridable, and make sure that all instance fields are included in the serialization process or explicitly marked by using the NonSerializedAttribute attribute.

Dependency: None

Notes:
@ghost ghost added the FxCop-Port label Nov 21, 2015
@ghost ghost added the Area-DesktopAnalyzers label Dec 4, 2015
@mavasani mavasani modified the milestones: 15.3, Unknown Apr 17, 2017
@Evangelink Evangelink mentioned this issue Nov 23, 2021
Open
31 tasks
@jeffhandley
Copy link
Member

This rule will not be ported since we are on a path toward having BinaryFormatter fully deprecated and removed from .NET.
See also: BinaryFormatter Obsoletion Strategy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
FxCop-Port Resolution-Won't Fix
Projects
None yet
Milestone
Unknown
Development

No branches or pull requests
3 participants
@jeffhandley @mavasani @Evangelink