NsDepCop
| NsDepCop | .NET Compiler Platform ("Roslyn") Analyzers | |
|---|---|---|
| - | 11 | |
| 184 | 1,577 | |
| - | 1.4% | |
| 5.8 | 9.4 | |
| about 1 year ago | 7 days ago | |
| C# | C# | |
| GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
NsDepCop
We haven't tracked posts mentioning NsDepCop yet.
Tracking mentions began in Dec 2020.
.NET Compiler Platform ("Roslyn") Analyzers
-
.NET Compiler Platform ("Roslyn") Analyzers VS Metalama - a user suggested alternative
2 projects | 7 Dec 2023
-
Microsoft.CodeAnalysis.BannedApiAnalyzers
See the following page
- What does a mature dotnet pipeline look like?
-
I wrote useful Microsoft ILogger<TCategoryName> analyzer, which helps you to find mistakes in your code
The other comment here is probably a good start. There may be some guidance over at https://github.com/dotnet/roslyn-analyzers on how to write high-performance analyzers. But your code is simple enough that I'm not sure it's a huge concern.
- Welcome to C# 11
- Something I've wanted for years... DisposeNotRequiredAttribute: Add way to mark IDisposable classes as not needing to be disposed
- Which linters are you using for CI environments?
-
Errors and suspicious code fragments in .NET 6 sources
Moreover, in the Roslyn Analyzers issue tracker, was created the task of developing a new diagnostic that would detect such cases.
-
Improving your code for style, quality, maintainability, design... with Roslyn Analyzers
Microsoft.CodeAnalysis.PublicApiAnalyzers: Helps library authors monitor changes to their public APIs (more info).
-
Library authors, be really careful with Type.GetMethod(string). It is a backwards compatibility nightmare.
Like the other person said, one way is to look at code analyzers, e.g. https://github.com/dotnet/roslyn-analyzers/blob/a0522afd52b25ad211298e308fd5bbc7734865e0/src/PerformanceSensitiveAnalyzers/CSharp/CodeFixes/AvoidAllocationWithArrayEmptyCodeFix.cs
What are some alternatives?
StyleCop - Analyzes C# source code to enforce a set of style and consistency rules.
Beat Pulse
CodeMaid - CodeMaid is an open source Visual Studio extension to cleanup and simplify our C#, C++, F#, VB, PHP, PowerShell, JSON, XAML, XML, ASP, HTML, CSS, LESS, SCSS, JavaScript and TypeScript coding.
Gendarme - Gendarme is a extensible rule-based tool to find problems in .NET applications and libraries. Gendarme inspects programs and libraries that contain code in ECMA CIL format (Mono and .NET) and looks for common problems with the code, problems that compiler do not typically check or have not historically checked.
Metrics-Net - The Metrics.NET library provides a way of instrumenting applications with custom metrics (timers, histograms, counters etc) that can be reported in various ways and can provide insights on what is happening inside a running application.
BenchmarkDotNet - Powerful .NET library for benchmarking
App.Metrics - App Metrics is an open-source and cross-platform .NET library used to record and report metrics within an application.