Reference Assistant for Visual Studio 11

Free

Removes unused references from C#, F#, VB.NET or VC++/CLI projects in the Visual Studio 11

(8) Review
Visual Studio
2012
Download (4,448)
5/9/2012
1.1.12130.850
View
E-mail Twitter del.icio.us Digg Facebook
Add To Favorites
Description
Reviews (8)
Q and A (1)
Sign in to Write a Review
Sort By:

by NickGK | May 21 2013

by Woon Cherk | April 28 2013

Does not work well with NUGET.

by dirq | February 19 2013

Woah. Bad. I tried using it in a .NET 4 web app. It gets 1 star for having a dialog, without which my project would have messed up. Pretty much every reference it said could be removed, I knew was used. So, no dice for this extension. Uninstalled.

by oasik | February 19 2013

I was hoping to use it with my MVC project, but unfortunately it removes references that are needed. Therefore I cannot recommend it :(

by Mustafa Gamal | February 13 2013

it is not working, in asp.net mvc it removes references to razor engine, which breaks the project

by ash2093 | January 31 2013

Keep up the good work.

by Matthias Friedrich | September 12 2012

Works great; except for web-projects, but this might be related to "hidden" references defined by web.config files or views, which are probably hard to find. I give five stars as a motivator to keep up the good work (-:

by grundt | August 23 2012

Great idea, and the extension functions just fine when it comes to identifying and removing references.
Unfortunately, it identifies some references as "unused" when in fact they are used.
At least that was my experience in VS2012, for a newly created ASP.NET MVC 4 Web Application project

Sign in to Start a Discussion


  • If a DLL depends on another DLL #2, does this tool know NOT to remove #2?
    2 Posts | Last Post June 07, 2013
    • For example, my Azure Web Role uses Application.dll, and application.dll requires paypal_base.dll.  Does this tool know NOT to remove paypal_base.dll, or will it remove paypal_base.dll, and a runtime exception will occur when application.dll code runs?
      
      Thanks!
    • No, it does not know to leave the secondary dependency. I just verified this in a project of mine. My project only references "First.dll" and "First.dll" only references "Second.dll" and this tool wanted to remove "Second.dll"
      
      I've heard resharper handles unused references more accurately.