Skip to content
Easily identify which dependencies can be removed from a .NET project
Branch: master
Clone or download
Latest commit 6d644eb Oct 5, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
build
src
test
.gitignore
Directory.Build.props Remove Buildalyzer dependency Sep 30, 2018
LICENSE
NuGet.Config Release v1.2.0 Apr 27, 2018
README.md Update readme Oct 5, 2018
ReferenceTrimmer.sln Produce a NuGet tools package Oct 5, 2018

README.md

ReferenceTrimmer

NuGet Version NuGet Downloads

Easily identify which dependencies can be removed from an MSBuild project.

How to install and run

  1. nuget install ReferenceTrimmer
  2. Note where NuGet specified it installed the package, which should match the location specified in your NuGet.config (it will look like "Installing package 'ReferenceTrimmer' to...")
  3. Navigate to the root directory to use for analysis
  4. Run ReferenceTrimmer.exe from the location noted in step 2. Within the package it's in the tools folder.

The program should then output which References, ProjectReferences, and PackageReferences should be removed from each project (if any).

Command-line arguments

All arguments are optional.

  -p, --path           Path from which to start searching for projects. Defaults to the current working directory.
  -c, --compile        Compile a project if its intermediate assembly doesn't exist.
  -r, --restore        Restore a project if its assets file doesn't exist and is needed to for PackageReference analysis.
  -b, --binlog         Creates a binlog if a Compile or Restore is needed. This can help with debugging failures.
  -m, --msbuildpath    Overrides the MsBuild tools path
You can’t perform that action at this time.