title: visual studio 2010 control library references
body: <p>I wrote a control library using visual studio 2010, I'll call it MyLibrary. MyLibrary references another control library I have that we'll call AnotherLibrary.  I also have a clean virtual machine (CVM) and I've added AnotherLibrary to the GAC on the CVM.  Using the CVM, I create a new WinForms project, add MyLibrary.dll to the toolbox, and drop one of the controls onto the form. Visual Studio will add MyLibrary.dll AND AnotherLibrary.dll to the references, even though AnotherLibrary.dll is in the GAC (and isn't needed).  I can remove AnotherLibrary.dll from the references and everything is fine.</p>
  
  <p>Is there a way to prevent visual studio from adding AnotherLibrary.dll in this scenario?</p>
  
  <p>Edit: I've given this some thought and I have an example. When you add a TabControl to a parent control in the designer, visual studio won't add System.Design to the references, even though the TabControl depends on it. So, surely there is a way to do this?</p>