title: Dependencies and DLL in Visual Studio Installer
body: <p>I am using VS2010's <strong>Visual Studio Installer</strong> to deploy my application to an <strong>MSI</strong>. </p>
  
  <p>I referenced numerous DLLs during development; some are 3rd parties, while some are system DLLs. Now during deployment, I do not know what to include or exclude. Visual Studio automatically included <strong>Detected Dependencies</strong> after I added the output .EXE but they are usually not sufficient to run the application. I often had to manually include the development's DLLs to the installed application folder.  Otherwise, <strong>eventvwr</strong> would just provides a generic <strong>CLR20r3</strong> error that only tells me missing DLLs but not indicating which one.</p>
  
  <p>It became a habit (a very bad habit, IMO) to include ALL references in my deployment project as they are referenced in my development project, but I guess uninstallation of the application may possibly remove System DLLs that causes problems to other application.</p>
  
  <p>So how would I know which DLLs to include manually in the deployment project, in addition to the <strong>Detected Dependencies</strong>?</p>