version numbering
-
if you have several projects in a solution that all compile to individual EXE's what do you do with version numbers?... keep them all in line with each other or have each EXE with its own independent version number?
I'd say that's up to the conscience of the individual church-goer. But it makes sense to me to have all different ones - why would the version number change on one part of the project, just because you updated another. Christian Graus - Microsoft MVP - C++
-
if you have several projects in a solution that all compile to individual EXE's what do you do with version numbers?... keep them all in line with each other or have each EXE with its own independent version number?
Two version numbers are within each module : File Version and Product Version. We tend to let the File Version float depending upon the particular module. The product versions typically are all the same for all modules of a particular product release. This way, you can look at a DLL, for eexample, and know which version of the DLL you have and also which version of the product it was intended to work with.
-
Two version numbers are within each module : File Version and Product Version. We tend to let the File Version float depending upon the particular module. The product versions typically are all the same for all modules of a particular product release. This way, you can look at a DLL, for eexample, and know which version of the DLL you have and also which version of the product it was intended to work with.