MikeNakis.AnalysisRules
1.1.321
dotnet add package MikeNakis.AnalysisRules --version 1.1.321
NuGet\Install-Package MikeNakis.AnalysisRules -Version 1.1.321
<PackageReference Include="MikeNakis.AnalysisRules" Version="1.1.321"> <PrivateAssets>all</PrivateAssets> <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference>
<PackageVersion Include="MikeNakis.AnalysisRules" Version="1.1.321" />
<PackageReference Include="MikeNakis.AnalysisRules"> <PrivateAssets>all</PrivateAssets> <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference>
paket add MikeNakis.AnalysisRules --version 1.1.321
#r "nuget: MikeNakis.AnalysisRules, 1.1.321"
#:package MikeNakis.AnalysisRules@1.1.321
#addin nuget:?package=MikeNakis.AnalysisRules&version=1.1.321
#tool nuget:?package=MikeNakis.AnalysisRules&version=1.1.321
MikeNakis.AnalysisRules
My very own™ code analysis rules for DotNet.
This package supplies the following files to projects that reference it:
.editorconfigAllCode.globalconfigProductionCode.globalconfigTestCode.globalconfig
The new files appear in a subdirectory called MikeNakisAnalysisRules under the project directory, and they are all
read-only.
The package also supplies a MikeNakisAnalysisRules property which points to the directory where the supplied files are
located, so they can be included as follows:
<ItemGroup>
<GlobalAnalyzerConfigFiles Include="$(MikeNakisAnalysisRules)AllCode.globalconfig" />
<GlobalAnalyzerConfigFiles Include="$(MikeNakisAnalysisRules)ProductionCode.globalconfig" />
</ItemGroup>
Unfortunately, the .editorconfig file cannot be included like that, so it is (automatically) copied from
MikeNakisAnalysisRules into the project directory. The copy is writable, so be careful not to modify it because any
edits you make to it will be lost next time the package is restored.
It is best to refrain from adding .editorconfig to .gitignore, so that if you ever change .editorconfig you have a
chance to take notice. Even if .editorconfig gets accidentally committed, next time the package is restored it will
appear as modified again, so you have more chances to take notice, and when you do eventually notice that you have been
losing the changes you have been making to it, you might still be able to find your lost changes in the git commit
history.
Learn more about Target Frameworks and .NET Standard.
This package has no dependencies.
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 |
|---|
No release notes. That's what the commit history is for.