What is the logic behind setting and using the Major, Minor and build numbers in a VB EXE project?
When I set the major to 7, the minor to 5 and the build to 101 then, when checking the version number in the properties window for a EXE (in explorer, right mouse click, properties, version), I get: 7.05 instead of 7.5.101 And the rest isn't being shown.
When I use P&D and check the file version in Setup.lst, it shows: 7.5.0.1 instead of 7.5.101.
I would like both versions to show the same, as 7.5.101
When I check the version numbers of other programs, like the DAO 3.51.1608, it shows the same (correct) version number in Properties and well as the Setup.lst.
Sometimes a version number looks like this: 3.51.1608.1001.
With four dots. But in VB Project Properties I cannot use the dots - only whole numbers.
Can some please explain to me the proper use of the version number?
When I set the major to 7, the minor to 5 and the build to 101 then, when checking the version number in the properties window for a EXE (in explorer, right mouse click, properties, version), I get: 7.05 instead of 7.5.101 And the rest isn't being shown.
When I use P&D and check the file version in Setup.lst, it shows: 7.5.0.1 instead of 7.5.101.
I would like both versions to show the same, as 7.5.101
When I check the version numbers of other programs, like the DAO 3.51.1608, it shows the same (correct) version number in Properties and well as the Setup.lst.
Sometimes a version number looks like this: 3.51.1608.1001.
With four dots. But in VB Project Properties I cannot use the dots - only whole numbers.
Can some please explain to me the proper use of the version number?