What is the proper way to handle assembly version?

Question

I am looking forward to implementing a daily build for an upcoming project.

But before doing that, I need to know how to properly version an assembly.

I have the following concerns:

• Should each assembly have an independent version number or should they all share the same version?
• Should I use a * version for build and revision?
• Is revision relevant to daily build?

Answer 1

We stamp all the assemblies within our products with the same version number using the following steps:

• Link all assemblies to an AssemblyInfoCommon.cs containing the version number info: see here for an example.

• Generate the AssemblyInfoCommon.cs file as part of the build using (in our case) the NAnt asminfo task, Cruise Control .NET and the SVN revision labeller

In our case, we don't use the * version. All deployed versions are built on the build server. We don't worry about version number on our desktops.