title: File versions of a large number of referenced assemblies
body: <p>My team and I are stuck on a version issue I do not think this has been answered before, so apologies if it has. I'll just talk about file version.</p>
  
  <p>We are working on a project that references a large number of assemblies (50+). These assemblies all have file versions of v.1.5.x.x and so on. </p>
  
  <p>A large change is being made to the project as a whole and the project version number is going to v.2.0.0.0. </p>
  
  <p>However, only minor modifications have been made to each of the referenced assemblies. Usually, the file version of these assemblies would go from v.1.5.x.0 to v.1.5.x.1, and so on. </p>
  
  <p>However, since we are making a large modification to the application, would it make more sense to set the file versions of all these assemblies to v.2.0.0.0? </p>
  
  <p>Looking at the .net assemblies, this seems to be what Microsoft do?</p>
  
  <p>What is the recommended approach?</p>