title: Removing Assembly file version dependency in .NET Project or Backward compatibility of "dll's with older versions
body: <p>I am stuck with assembly compatibility problems with my project.</p>
  
  <p>1) I have a .NET project, where i specify a assembly version . "Major part.Minor part.Build part.Revision part".
  2) For the next build, assembly version is incremented.
  3) There are many files (dll) which doesn't have any changes but their assembly version is updated.
  4) The newer "dll" files are not compatible with older versions of same dll files.</p>
  
  <p>I tried to get more information to solve this online.</p>
  
  <p>1) There is a concept of publisher policy , where i can specify the older version number.
  2) Manifest file to be added in the project for all the classes and provide the range of possible version which can be used if current version is not available.</p>
  
  <p>I am not sure, if i am doing right. What is the difference between publisher policy approach and manifest file approach.</p>
  
  <p>Is it possible to do the backward compatible for "dll's".</p>