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.

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

Clear current search query, filters, and sorts
987 Open 2,507 Closed
987 Open 2,507 Closed
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
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Analyzers should be run in an isolated environment to prevent malicious code
#6847 opened Aug 9, 2023 by KAW0
4 👀 4
CA2000: Rule does not trigger for IDisposable objects returned from factory methods in a different assembly
#7590 opened Feb 27, 2025 by ozziepeeps
1 👀 2
CA2000 false positive inside foreach loop
#7047 opened Nov 21, 2023 by batkaevruslan
👀 2
Prefer const for literals that are assigned upon declaration and not re-assigned Feature Request help wanted The issue is up-for-grabs, and can be claimed by commenting
#7492 opened Aug 29, 2024 by Bartleby2718
👀 1
CA1508: false positive Area-Microsoft.CodeAnalysis.NetAnalyzers Category-Maintainability False_Positive A diagnostic is reported for non-problematic case 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)
#7152 opened Jan 18, 2024 by emperador-ming Unknown
1 👀 1
Revisit public API analyzer design
#5787 opened Jan 10, 2022 by tmat
14 👀 1
Can't ban namespaces
#7340 opened Jul 1, 2024 by gilfrenkel89
2 👀 1
Recommend use of null instead of default when assigning an expression to a nullable type. Feature Request
#6208 opened Oct 17, 2022 by mrpmorris
2 👀 1
GetCSharpResultAt/GetBasicResultAt test helpers Discussion help wanted The issue is up-for-grabs, and can be claimed by commenting Test
#3088 opened Dec 4, 2019 by Evangelink Unknown
2 👀 1
Add analyzer to find incorrect use of locks in async methods Area-Roslyn.Diagnostics.Analyzers Feature Request
#314 opened Oct 16, 2015 by mattwar Unknown
3
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
#356 opened Nov 11, 2015 by srivatsn Unknown
2
Port FxCop rule CA1004: GenericMethodsShouldProvideTypeParameter FxCop-Port
#370 opened Nov 21, 2015 by ghost Unknown
Port FxCop rule CA1010: CollectionsShouldImplementGenericInterface FxCop-Port Needs-Fixer
#374 opened Nov 21, 2015 by ghost Unknown
3
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
1
@Evangelink
11
Port FxCop rule CA1030: UseEventsWhereAppropriate FxCop-Port Needs-Fixer
#380 opened Nov 21, 2015 by ghost Unknown
1
1
Port FxCop rule CA1044: PropertiesShouldNotBeWriteOnly FxCop-Port Needs-Fixer
#390 opened Nov 21, 2015 by ghost Unknown
1
Port FxCop rule CA1057: StringUriOverloadsCallSystemUriOverloads Blocked FxCop-Port Needs-Review
#401 opened Nov 21, 2015 by ghost Unknown
Port FxCop rule CA1063: ImplementIDisposableCorrectly FxCop-Port Needs-Fixer
#405 opened Nov 21, 2015 by ghost Unknown
4
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
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 CA1306: SetLocaleForDataTypes Blocked DataFlow Feature Request FxCop-Port Needs-Review
#414 opened Nov 21, 2015 by ghost Unknown
Port FxCop rule CA1307: SpecifyStringComparison FxCop-Port Needs-Fixer
#415 opened Nov 21, 2015 by ghost Unknown
9
Port FxCop rule CA1308: NormalizeStringsToUppercase Area-Microsoft.CodeAnalysis.NetAnalyzers FxCop-Port Needs-Fixer
#416 opened Nov 21, 2015 by ghost Unknown
1
1
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
IDE0306 triggers for invalid case and the fix generate wrong code
#7596 opened Mar 8, 2025 by wiz0u
ProTip! Exclude everything labeled bug with -label:bug.