Different version formats for .Net & win32 components

9 03 2009

For a win32 dll or exe , the  fileversion attribute means following:


Whereas, a .Net component has different interpretation of these numbers.  i.e.


This means, if you have an  exe or dll with fileversion from a vc++ project, then corresponding assemblyversion for a .Net exe or dll for same build would be:

This was causing little confusion while I was working with FinalBuilder to version all project executables before applying MSBuild.  Right now, I have kept consistent version format for all project types  and am interpreting them as win32 style version information.

Any opinions?