Hi, all :)
Some of you might probably laugh at me shortly, but please dont flame me. I have to admit, I dont fully understand the different structures of versions information. In most cases the version is displayed 1.00, but in some cases it is displayed 1, 0, 0, 0, like in the VC++ version resource. I am quite sure that these both examples display the same version, but why are there two different structures? And is there any version difference between 1.10 and 1, 1, 0, 0?
I have also very often seen the Build keyword followed by an integer number, but what does it mean? Does it mean the number of times the product was compiled or updated?
I am sorry if I trouble you with this common concept, but I have been confused in some cases and I want to be sure that I am not missing anything.
The build + a number is how many times you've built (compiled) your project. Its another way to keep track of different versions in addition to user supplied versions (ex: version 1.2).
Ok Thanks :)
But what about the diffrent version structures, and is there any version difference between 1.10 and 1, 1, 0, 0? :(
sorry... another question, related to the Build question. Do you reset the Build number every time you update your project to a newer version, like ex. from "1.0" to "1.1"?
I'm not so sure about these jokers, but I don't.
hmm... what do you mean by "jokers"?
nope, we edit the build number or the patch number:
e.g.: Linux kernel 2.5.73
2: major build
5: minor build
you could write: Perl 5.8.0 Build 830
5: major build
8: minor build
or u own prog: prog 22.214.171.124.7
12: major build
68: minor build
45: build 45
7: version 7
I doesn't metter, how u write down the version information (but that's for sure, that nobody likes: 126.96.36.199.7)
the best way is: major build.minor build.patch (2.5.73)
or major buil.minor build.patch Build 80 (5.8.0 Build 80)
Thanx and sorry for my late respons, I have been a way for a while :)