Kiruyuto.DotNet.Config
2.3.8
dotnet add package Kiruyuto.DotNet.Config --version 2.3.8
NuGet\Install-Package Kiruyuto.DotNet.Config -Version 2.3.8
<PackageReference Include="Kiruyuto.DotNet.Config" Version="2.3.8"> <PrivateAssets>all</PrivateAssets> <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference>
<PackageVersion Include="Kiruyuto.DotNet.Config" Version="2.3.8" />
<PackageReference Include="Kiruyuto.DotNet.Config"> <PrivateAssets>all</PrivateAssets> <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference>
paket add Kiruyuto.DotNet.Config --version 2.3.8
#r "nuget: Kiruyuto.DotNet.Config, 2.3.8"
#:package Kiruyuto.DotNet.Config@2.3.8
#addin nuget:?package=Kiruyuto.DotNet.Config&version=2.3.8
#tool nuget:?package=Kiruyuto.DotNet.Config&version=2.3.8
.NET-Config
Personal set of rules and analyzers distributed as a NuGet package to share configuration across .NET projects.
Heavily based on Gérald Barré (@Meziantou)'s "Sharing coding style and Roslyn analyzers across projects" post and his CodingStandard repository.
This config contains rules changed and fine-tuned to my personal and work needs as well as preferences.
Usage
Add the NuGet package to your project, and the configs will be automatically imported.
It is recommended to use Directory.Build.props in your project over per .csproj configuration
Structure overview
- Dependencies can be found in Kiruyuto.DotNet.Config.csproj
.globalconfigrule configurations are located infiles/directory.propsfiles are located inbuild/directory. These are split into 'categories' for improved maintainability
Building & Local testing
Run this command in the repository root to generate .nupkg file in local-packages/ directory:
dotnet pack Kiruyuto.DotNet.Config/Kiruyuto.DotNet.Config.csproj -c Release -o ./local-packages -p:PackageVersion=0.0.1
After that, you can add the generated package as a local source in your projects to test it out.
dotnet nuget add source "$(cygpath -w "$(pwd)/local-packages")" -n KiruyutoDotNetConfigLocal
Then run this command to check if source was added:
dotnet nuget list source
You can run this one-liner to do above steps at once:
dotnet pack Kiruyuto.DotNet.Config/Kiruyuto.DotNet.Config.csproj -c Release -o ./local-packages -p:PackageVersion=0.0.1 && dotnet nuget add source "$(cygpath -w "$(pwd)/local-packages")" -n KiruyutoDotNetConfigLocal && dotnet nuget list source
When you are done testing and want to remove the local source, run:
dotnet nuget remove source KiruyutoDotNetConfigLocal
Contributing
See CONTRIBUTING.md for details.
Learn more about Target Frameworks and .NET Standard.
-
net10.0
- AsyncFixer (>= 2.1.0)
- Microsoft.CodeAnalysis.BannedApiAnalyzers (>= 3.3.4)
- Microsoft.EntityFrameworkCore.Analyzers (>= 10.0.2)
- Microsoft.VisualStudio.Threading.Analyzers (>= 17.14.15)
- SonarAnalyzer.CSharp (>= 10.19.0.132793)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 2.3.8 | 573 | 2/7/2026 |
| 2.3.7 | 564 | 1/30/2026 |
| 2.3.6 | 962 | 1/14/2026 |
| 2.3.5 | 272 | 1/12/2026 |
| 2.3.4 | 299 | 1/8/2026 |
| 2.3.3 | 148 | 1/6/2026 |
| 2.3.2 | 123 | 1/6/2026 |
| 2.3.1 | 123 | 1/6/2026 |
| 2.3.0 | 122 | 1/6/2026 |
| 2.2.1 | 136 | 1/4/2026 |
| 2.2.0 | 130 | 1/4/2026 |
| 2.1.7 | 132 | 1/4/2026 |
| 2.1.6 | 130 | 1/1/2026 |
| 2.1.5 | 128 | 1/1/2026 |
| 2.1.4 | 129 | 12/31/2025 |
| 2.1.3 | 123 | 12/31/2025 |
| 2.1.2 | 123 | 12/31/2025 |
| 2.1.1 | 125 | 12/31/2025 |
| 2.1.0 | 129 | 12/31/2025 |
| 2.0.0 | 124 | 12/31/2025 |