title: How to manage version control of common DLLs across multiple .NET projects?
body: <p>Following SO thread shows <a href="https://stackoverflow.com/questions/1700568/managing-net-assembly-dependencies-by-dll-reference-rather-than-by-project-refer">Managing DLL references in multiple projects across different solutions</a>. Additionally I want to know how to manage the version control for these dependency DLLs ?</p>
  
  <p>Should the DLL (which is published to other external projects) be committed too, every time code change happens ? </p>