Lindhart.DependencyCop
0.1.0
dotnet add package Lindhart.DependencyCop --version 0.1.0
NuGet\Install-Package Lindhart.DependencyCop -Version 0.1.0
<PackageReference Include="Lindhart.DependencyCop" Version="0.1.0"> <PrivateAssets>all</PrivateAssets> <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference>
<PackageVersion Include="Lindhart.DependencyCop" Version="0.1.0" />
<PackageReference Include="Lindhart.DependencyCop"> <PrivateAssets>all</PrivateAssets> <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference>
paket add Lindhart.DependencyCop --version 0.1.0
#r "nuget: Lindhart.DependencyCop, 0.1.0"
#:package Lindhart.DependencyCop@0.1.0
#addin nuget:?package=Lindhart.DependencyCop&version=0.1.0
#tool nuget:?package=Lindhart.DependencyCop&version=0.1.0
DependencyCop
This package is a fork of the original Liversen.DependencyCop by Lars Iversen, enhanced with automatic code fixing capabilities.
Migrating from Liversen.DependencyCop? All rule IDs remain unchanged (DC1001, DC1002, DC1003, DC1004), so your existing configurations will continue to work without modification.
This package contains a number of Roslyn analyzer rules using the .NET Compiler Platform. The rules enforce certain restrictions on dependencies between code in different namespaces.
Rules
Rule DC1001: Using namespace statements must not reference disallowed namespaces
Rule DC1002: Code must not refer code in descendant namespaces
Rule DC1003: Code must not contain namespace cycles
Rule DC1004: Rule DC1001 is not configured
📖 For complete documentation, rationale, and details about the fork, see the main repository README.
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 | |
|---|---|---|---|
| 0.1.0 | 101 | 5/1/2026 |