3 ms·
I thought it was generally considered good practice to put extension methods into static classes in their own file. So like `FooExtensions.cs` if you are writi
by jdmichal 5y ago
I thought it was generally considered good practice to put extension methods into static classes in their own file. So like `FooExtensions.cs` if you are writing extensions for the `Foo` class.
I would consider this the same: Project should have a `GlobalUsings.cs` file.
Does C# have any linters available that could enforce such a conventions?
- int_19h 5y agoC# has a framework in-place to facilitate workspace-specific linters, so even if one doesn't exist, it could be written very easily (and premade ones are sure to appear quickly). https://docs.microsoft.com/en-us/dotnet/csharp/roslyn-sdk/tutorials/how-to-write-csharp-analyzer-code-fix https://docs.microsoft.com/en-us/dotnet/csharp/roslyn-sdk/tu...