-
Notifications
You must be signed in to change notification settings - Fork 470
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
Label
Projects
Milestones
Assignee
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
Create analyzer to correctly guide users using GetDeclaredSymbol() and GetSymbolInfo()
Area-Microsoft.CodeAnalysis.Analyzers
Feature Request
help wanted
The issue is up-for-grabs, and can be claimed by commenting
Advise against mixing both C# and VB analyzers in the same dll.
Area-Microsoft.CodeAnalysis.Analyzers
Feature Request
help wanted
The issue is up-for-grabs, and can be claimed by commenting
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
Replacing an explicit declaration with an equivalent compiler-generated should not trigger RS0017
Area-Microsoft.CodeAnalysis.PublicApiAnalyzers
help wanted
The issue is up-for-grabs, and can be claimed by commenting
Test
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
.NET 9 perf improvements to Enumerable.Any() invalidates rule CA1860
#7576
opened Feb 14, 2025 by
Muximize
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
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)
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)
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
Previous Next
ProTip!
What’s not been updated in a month: updated:<2025-01-14.