title: Visual Studio: different ocx file version number for new OS?
body: <p>I'm looking for general advice.  I created a Visual Studio 2010 project that outputs an ocx file that is used on XP and Vista machines.  The DLL on which it depends has been updated on our Win7 machines.  I simply needed to rebuild for Win7 using the exact same code with an updated .lib file.  I created a second project configuration (ReleaseW7) and it only differs from the original project config (Release) in that it points to the new .lib.</p>
  
  <p>So now I have 2 files both named xx.ocx.  Besides looking at the name of the folder each file resides in (or looking at the creation time of each) there is no way to determine which is which.  I thought of using different file version numbers but as far as I can tell (and I'm relatively new to this so I could certainly be wrong) that would require two separate projects each with a slightly modified resource (.rc) file, instead of simply having two configurations within the same project.  If nothing more, that seems like a waste of hard drive space.  It also feels like the "wrong" way of using file version numbers</p>
  
  <p>Is there a cleaner or more "standard" way of handling this?  All I really want is a way for the folks who install the ocx and support the end user to know for certain that they are working with the correct file.</p>