Dot net assembly versioning

[Coder]

I notice that MS says the version numbers have the following format:
<major version>.<minor version>.<build number>.<revision>

If you give a assembly version as "1.0.*", the two latest numbers should
increment.

However, the latest number (rightmost/revision) is the fastest moving, which
increments for every build. Shouldn't that be the Build no, not the
revision no ?

And when does the 3rd number (now called build number, but shouldn't it be
the revision no) increments ?

Anybody know anything ?



best regards

Terje

 

[Mickey Williams]

In some of the older documentation, the revision portion was called the QFE,
which was clearer (I think). Its semantics are that an incrementing value
indicates a non-breaking change.

Today the reality is that generally people that don't use strong names
accept the default behavior for the last two segments, which is:
- the third segment is incremented every day (from 1/1/2000)
- the fourth segment is incremented every two seconds (from midnight)

 

[Eric Newton]

Another note:
C# and VB.Net's "auto incrementing" have different incrementing formulas...

 

[Grant Richins [MS]]

Another note:
C# and VB.Net's "auto incrementing" have different incrementing formulas...

I would like proof of that because they both call the same DLL (alink.dll)
to do the auto-incrementing.