title: solving an assembly conflict issue -- Visual Studio project reference + specific version
body: <p><strong>SHORT QUESTION</strong>: How can I use a project reference but build my assembly so the reference is a specific version reference?</p>
  
  <hr>
  
  <p><strong>LONG QUESTION (more details)</strong>: We're working on a modular setup for one of our applications.  Different sets of software components are loaded, along with their dependencies, into isolated AppDomains.</p>
  
  <p>There are libraries that might be referenced by different components.  In some cases, we're running into assembly conflicts.  IE we've got the newest version of a library loaded AND an old version and one of the Types being used (components are instantiated using reflection) needs to grab something that's no longer in the new version, ie a type whose name has been changed or something, so a TypeLoadException or whatever is thrown because it's trying to pull the type from the new version even though the old version has also been explicitly loaded.  The way to avoid problems like this, it seems, is to reference specific versions.</p>
  
  <p>As far as I understand it, the way to set a reference up this way from Visual Studio is to set the Specific Version property on the reference to true, and this can only be done when you're referencing a DLL as a file reference NOT as a project reference.  The problem is that these other libraries are still in development so I'll potentially need to be debugging them too during tests.  I want to be able to do all the nice stuff project references let you do ie navigate to definitions (mostly that, really, so i can set breakpoints while debugging and etc).</p>
  
  <hr>
  
  <p><strong>&lt;Edit&gt;</strong> In response to Slak's question, yes I do need to run both versions.  It's explained in the LONG QUESTION.</p>