1. Herfried K. Wagner’s VB.Any
  2. .NET
  3. Frequently Asked Questions

Structure of version numbers and methods to determine the version number

Structure of version numbers and methods to determine the version number
<URL:https://dotnet.currifex.org/dotnet/faqs/versioning/en/>
----------------------------------------------------------------------------

Structure of version numbers and methods to determine the version number

Basic information on versioning:

Managing Versions of an Application
<URL:http://msdn.microsoft.com/library/en-us/dndotnet/html/managevers.asp>

Team Development with Visual Studio .NET and Visual SourceSafe
<URL:http://msdn.microsoft.com/library/en-us/dnbda/html/tdlg_ch5.asp>

.NET Framework Tutorials -- Versioning Components
<URL:http://msdn.microsoft.com/library/en-us/cptutorials/html/versioning_components.asp>

Parts of the version number:

Main version
    "Product" version.

Sub version
    Sub version, for example Service Pack.

Build
    During development, auto-increment.

Revision
    Hotfix or Quick Fix Engineering (QFE).

When using auto incrementation of numbers, the build number contains the
number of days since January, 2000; the revision contains the number of
seconds since midnight divided by 2.

The version number can be changed in the file "AssemblyInfo.vb". The
version number will updated automatically when re-opening the solution.

Getting the program version number:

\\\
MsgBox( _
    System.Reflection.Assembly.GetExecutingAssembly( _
    ).GetName().Version.ToString() _
)
///

- or -

\\\
MsgBox( _
    System.Windows.Forms.Application.ProductVersion.ToString() _
)
///

Version information for executable files and DLLs can be obtained by using
the 'System.Diagnostics.FileVersionInfo' class.

VB6 style versioning
<URL:http://www.jmedved.com/?page=vbnet_vb6ver>

How to auto-increment assembly version using a custom MSBuild task 
<URL:http://weblogs.asp.net/bradleyb/archive/2005/12/02/432150.aspx>