Different version formats for .Net & win32 components

9 03 2009

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

majorversion.minorversion.releaseversion.buildversion

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

majorversion.minorversion.buildnumber.revision

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

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?

Advertisements

Actions

Information

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s




%d bloggers like this: