Remove unused references (!= "using")

How can I find and delete unused references in my projects?

I know you can easily remove the using statements in vs 2008, but this doesn't remove the actual reference in your projects. The referenced dll will still be copied in your bin/setup package.

*Note: see http://www.jetbrains.net/devnet/message/5244658 for another version of this answer.

Reading through the posts, it looks like there is some confusion as to the original question. Let me take a stab at it.

The original post is really asking the question: "How do I identify and remove references from one Visual Studio project to other projects/assemblies that are not in use?" The poster wants the assemblies to no longer appear as part of the build output.

In this case, ReSharper can help you identify them, but you have to remove them yourself.

To do this, open up the References inth Solution Browser, right mouse click on each referenced assembly, and pick "Find Dependent Code". See:

http://www.jetbrains.com/resharper/features/navigation_search.html#Find_ReferencedDependent_Code

You will either get:

1. A list of the dependencies on that Reference in a browser window, or

2. A dialog telling you "Code dependent on module XXXXXXX was not found.".

If you get the the second result, you can then right mouse click the Reference, select Remove, and remove it from your project.

While you have to to this "manually", i.e. one reference at a time, it will get the job done. If anyone has automated this in some manner I am interested in hearing how it was done.

You can pretty much ignore the ones in the .Net Framework as they don't normally get copied to your build output (typically - although not necessarily true for Silverlight apps).

Some posts seem to be answering the question: "How do I remove using clauses (C#) from a source code file that are not needed to resolve any references within that file".

In this case, ReSharper does help in a couple ways:

1. Identifies unused using clauses for you during on the fly error detection. They appear as Code Inspection Warnings - the code will appear greyed out (be default) in the file and ReSharper will provide a Hint to remove it:

   http://www.jetbrains.com/resharper/features/code_analysis.html#On-the-fly_Error_Detection

2. Allows you to automatically remove them as part of the Code Cleanup Process:

   http://www.jetbrains.com/resharper/features/code_formatting.html#Optimizing_Namespace_Import_Directives

Finally, realize that ReSharper does static code analysis on your solution. So, if you have a dynamic reference to the assembly - say through reflection or an assembly that is dynamically loaded at runtime and accessed through an interface - it won't pick it up. There is no substitute for understanding your code base and the project dependencies as you work on your project. I do find the ReSharper features very useful.

you can use the 'Remove Unused References' extension I wrote:

http://visualstudiogallery.msdn.microsoft.com/9811e528-cfa8-4fe7-9dd1-4021978b5097

Removing unused references is a feature Visual Studio 2008 already supports. Unfortunately, only for VB .NET projects.

I have opened a suggestion on Microsoft Connect to get this feature for C# projects too:

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=510326

If you like this feature as well then you might vote my suggestion.

Try this one: Reference Assistant

> Summary > > Reference Assistant helps to remove unused references from C#, F#, > VB.NET or VC++/CLI projects in the Visual Studio 2010.

ReSharper will do this for you (and so so much more!)

ReSharper 6.1 will include these features:

• Optimize references: analyze your assembly references and their usages in code, get list of redundant references and remove them.

• Remove Unused References: quick refactoring to remove redundant assembly references.

• Safe delete on assembly references: will delete assembly references if all of them are redundant, otherwise dispalies usages and can remove only redundant assembly references of the selected list.

I done this without extension in the VS 2010 Ultimate Architecture->Generate Dependency Graph->By Assembly, it shows used assemblies, and manually removed unused references.

I have a free answer that works in any version of Visual Studio and any Framework version. It doesn't remove the unused references, but it identifies them.

You can use Telerik JustDecompile on your project dll. Just open the dll in JustDecompile and go under References to see what is actually used in the compiled dll.

Given that VisualStudio (or is it msbuild?) detects unused references and doesn't include them in the output file, you can write a script which parses the references out of the csproj, and compares that with the referenced Assemblies detected by reflexion on the project output.

If you're motivated...

I think that are copied in bin, because in the project that removed the reference have reference o other project that have the same reference...

If you know which references are not used you can remove them manually.
In Solution Explorer, right-click the reference in the References node, and then click Remove.