title: Referencing different versions of the same assembly
body: <p>If A references assembly B 1.1 and C, and C references B 1.2, how do you avoid assembly conflicts?</p>
  
  <p>I nievely assumed C's references would be encapsulated away and would not cause any problems, but it appears all the dll's are copied to the bin, which is where the problem occurs.</p>
  
  <p>I understand the two ways around this are to use the GAC or assembly bindings? The GAC doesn't seem like the best approach to me, as I don't like assuming dlls will be there, I prefer to reference dlls from a lib directory in my solution.</p>
  
  <p>Where as assembly bindings don't seem robust to me, what if one version of the assembly has functionality that the other doesn't, will this not produce problems?</p>
  
  <hr>
  
  <p>In my case its because I'm using a 3rd party dll uses a older version of nHibernate, than I'm using myself.</p>