.NET version numbers, order of build and revision

  • Thread starter Thread starter Lasse Vågsæther Karlsen
  • Start date Start date
L

Lasse Vågsæther Karlsen

I have seen this question posted on the web but I can't seem to find a
definite answer for this.

What is the thinking behind switching the order of version numbers from
what, at least I, consider to be the norm?

ie. this is what I expect:

major.minor.revision.build

and this is how .NET specifies them:

major.minor.build.revision

What is the point/description of build and revision in this?

My thinking, which just plain looks wrong, goes something like this:
"Each time I build I increase the revision number, and each time I
release a revision I increase the build number".

Should I use the numbers another way?
 
I believe this is more a problem of semantics than anything else. I just
think of it this way

major - RTM build with major feature changes
minor - RTM build with minor feature changes
build - Release considered for testing (pinned released)
revision - Any compile

It could be that you consider a build each compile, which is fine. But I
would not try altering the way the numbering works; I would just mentally
flip the ideas in your mind.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

*************************************************
| Think outside the box!
|
*************************************************
 
Cowboy said:
I believe this is more a problem of semantics than anything else. I just
think of it this way

major - RTM build with major feature changes
minor - RTM build with minor feature changes
build - Release considered for testing (pinned released)
revision - Any compile

It could be that you consider a build each compile, which is fine. But I
would not try altering the way the numbering works; I would just mentally
flip the ideas in your mind.
Click to expand...

I have no problems doing that, and in fact I'm already doing it. I just
discovered the reverse ordering when trying to set up FinalBuilder to
increase the build number (or revision, as it's called) for each build.

I just wondered if there was a good reason for switching it that I
didn't know of, sort of like discovering that pigs can fly a while after
wondering why bacon has suddenly become so expensive :)
 
Back
Top