ReferenceProtector 1.0.4-prerelease

ReferenceProtector

Protect from unwanted dependencies in your repository. As repo gets bigger - there's often a need to secure from bad dependencies between projects.

Rules

The following warnings are generated by this package:

How to use

Add a package reference to the ReferenceProtector package in your projects, or as a common package reference in the repo's Directory.Packages.props.

If you're using Central Package Management, you can use it as a GlobalPackageReference in your Directory.Packages.props to apply it to the entire repo.

  <ItemGroup>
    <GlobalPackageReference Include="ReferenceProtector" Version="{LatestVersion}" />
  </ItemGroup>

Create a .json file somewhere in your repository that will contain dependency rules, and provide full path to this file in MSBuild property for specific project, or for all projects. For example, placing DependencyRules.json file in the root of the repo, you can update Directpry.Build.props (assuming it's also in the root) with <DependencyRulesFile>$(MSBuildThisFileDirectory)DependencyRules.json</DependencyRulesFile>. You can also provide it via command line like /p:DependencyRulesFile=...

Schema of the rules file is as follows:

{
    "ProjectDependencies": [
    {
        "From": "",
        "To": "",
        "Policy": "",
        "LinkType": "",
        "Description": "",
        "Exceptions": [
            {
                "From": "",
                "To": "",
                "Justification": ""
            },
            // ...
        ]
    },
    // ...
    ]
}

Top ProjectDependencies object will contain a list of rules to validate against. Each rule has the following schema:

• From / To - Full path regex for source and target projects to be matched.
• Policy - enum with values Allowed / Forbidden. Describes whether link between From and To projects should be allowed or forbidden
• LinkType - enum with values Direct / Transitive / DirectOrTransitive. Specifies whether link between From and To projects is expected to be direct, transitive or both
• Description - human readable explanation for this policy rule. Will be displayed in a build warning if policy is violated (rule RP0004).
• Exceptions (Optional) - list of exceptions from this policy (can be due to tech debt, or for any other reason).

Matching logic

Each reference between the projects during the build is evaluated against provided list of policies. First each pair of dependent projects is evaluated against From and To patterns, based on their full path. If the match is successful - their link type is evaluated: if current pair has a direct dependency on each other and LinkType value is Direct or DirectOrTransient - the match is successful, otherwise (the dependency is transient) - LinkType should be Transient or DirectOrTransient for the match to be successful. Then we exceptions are evaluated using the same pattern matching logic with From and To fields. The decision logic is as follows

• If current Policy value is Forbidden - the rule is considered violated if no exceptions were matched
• If current Policy value is Allowed - the rule is considered violated if there are any matched exceptions

Violations of the rule will produce RT0004 warning during build.

Examples

Below are few examples of potential rules

Don't allow external dependencies from projects in Infrastructure folder

{
    "description": "Infrastructure referencing application logic is fordbidden",
    "Policy": "forbidden",
    "LinkType": "DirectOrTransient",
    "from": "*\\Infrastructure\\*",
    "to": "*",
    "exceptions": [
    {
        "from": "*\\Infrastructure\\*",
        "to": "*\\Infrastructure\\*",
        "justification": "Infrastructure projects can reference each other"
    },
    {
        "from": "*Tests.csproj",
        "to": "*",
        "justification": "tech debt <work item link>"
    },
    {
        "from": "*",
        "to": "LegacyDependency.csproj",
        "justification": "tech debt <work item link>"
    }
    ]
},

Allow referencing Common projects

    {
      "description": "Referencing Common is ok",
      "Policy": "allowed",
      "LinkType": "DirectOrTransient",
      "from": "*",
      "to": "*\\Common.csproj"
    },

How it works

First - MSBuild task with gather all direct / indirect project references and dump them into a file (typically in obj/Debug/ folder), named references.tsv. During the second stage - Roslyn analyzer will read this file and match it against the dependency rules, defined in a file from <DependencyRulesFile> property. Corresponding diagnostics will be produced if violations are found.