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)

--
Mickey Williams
Author, "Microsoft Visual C# .NET Core Reference", MS Press
www.servergeek.com
"Coder" <[e-mail]> wrote in message
news:eX**************@tk2msftngp13.phx.gbl...

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

[Eric Newton]

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

--
Eric Newton
C#/ASP Application Developer
er**@cc.ensoft-software.com [remove the first "CC."]

"Mickey Williams" <my first name at servergeek.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

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)

--
Mickey Williams
Author, "Microsoft Visual C# .NET Core Reference", MS Press
www.servergeek.com
"Coder" <[e-mail]> wrote in message
news:eX**************@tk2msftngp13.phx.gbl...

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

[Grant Richins [MS]]

"Eric Newton" <er**@cc.ensoft-software.com> wrote in message
news:O9*************@TK2MSFTNGP11.phx.gbl...

Another note:
C# and VB.Net's "auto incrementing" have different incrementing formulas...
--
Eric Newton
C#/ASP Application Developer
er**@cc.ensoft-software.com [remove the first "CC."]

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

--
--Grant
This posting is provided "AS IS" with no warranties, and confers no rights.