Thanks to visit codestin.com
Credit goes to github.com

Skip to content

WFO1000 Analyzer: False positives on static properties of components #13206

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

Closed
Tracked by #13160 ...
KlausLoeffelmann opened this issue Mar 30, 2025 · 0 comments
Closed
Tracked by #13160 ...
Assignees
Labels
area-Analyzers/CodeFixes A Roslyn Analyzer is either needed for the context, needs to be scope extended or fixed.
Milestone

Comments

@KlausLoeffelmann
Copy link
Member

KlausLoeffelmann commented Mar 30, 2025

The WFO1000 security analyzer flags static properties of components, which are not used for serialization. This results in false positives.

Example:

public class CustomControl2 : Control 
{
    public static string? Value1 { get; set; }
    public static string? Value2 { get; private set; }
}

Impact:
This affects custom controls and generates unnecessary warnings, hindering productivity.

Replaces a part of the Bug of #12476.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Analyzers/CodeFixes A Roslyn Analyzer is either needed for the context, needs to be scope extended or fixed.
Projects
None yet
Development

No branches or pull requests

3 participants