Skip to content

Issues: dotnet/roslyn-analyzers

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

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

MEF best practices analyzers Feature Request Needs-Proposal A proposal defining the desired behavior is needed before review/approval process can begin
#5358 opened Aug 8, 2021 by sharwell Unknown
Port FxCop rule CA1011: ConsiderPassingBaseTypesAsParameters Bug The product is not behaving according to its current intended design FxCop-Port help wanted The issue is up-for-grabs, and can be claimed by commenting
#375 opened Nov 21, 2015 by ghost Unknown
Port FxCop rule CA1301: AvoidDuplicateAccelerators Approved-Rule Indicates if the new proposed rule has been approved to move to implementation phase FxCop-Port help wanted The issue is up-for-grabs, and can be claimed by commenting
#409 opened Nov 21, 2015 by ghost Unknown
Port FxCop rule CA1404: CallGetLastErrorImmediatelyAfterPInvoke Approved-Rule Indicates if the new proposed rule has been approved to move to implementation phase FxCop-Port help wanted The issue is up-for-grabs, and can be claimed by commenting Priority:2 Moderately important
#420 opened Nov 21, 2015 by ghost .NET vNext
Port FxCop rule CA1409: ComVisibleTypesShouldBeCreatable Approved-Rule Indicates if the new proposed rule has been approved to move to implementation phase FxCop-Port help wanted The issue is up-for-grabs, and can be claimed by commenting Priority:3 Nice to have (suitable for disabled by default rules and ported FxCop rules)
#425 opened Nov 21, 2015 by ghost .NET vNext
Port FxCop rule CA1412: MarkComSourceInterfacesAsIDispatch Approved-Rule Indicates if the new proposed rule has been approved to move to implementation phase FxCop-Port help wanted The issue is up-for-grabs, and can be claimed by commenting Priority:3 Nice to have (suitable for disabled by default rules and ported FxCop rules)
#428 opened Nov 21, 2015 by ghost .NET vNext
Port FxCop rule CA1414: MarkBooleanPInvokeArgumentsWithMarshalAs Approved-Rule Indicates if the new proposed rule has been approved to move to implementation phase FxCop-Port help wanted The issue is up-for-grabs, and can be claimed by commenting Priority:2 Moderately important
#430 opened Nov 21, 2015 by ghost .NET vNext
ProTip! Find all open issues with in progress development work with linked:pr.