Question: Does the build number always increment no matter the version or does the build number resets to 1 for every new version?
Question: Does the build number always increment no matter the version or does the build number resets to 1 for every new version?
The meaning of version numbers can vary across projects.
One common scheme is Semantic Versioning, which divides the version number into three parts:
MAJOR.MINOR.PATCH*MAJORis incremented when there are backwards incompatible changes.MINORis incremented when new features are added in a backwards compatible way.PATCHis incremented for smaller big fixes.- Each number is reset to zero when a higher level number is incremented.
* It's a bit more complex than this, but this is the gist.
AFAIK, build numbers and version numbers are usually seperate: Versions follow builds not the other way around.
You can build the same version multiple times. And no, versions are usually tied to branches and if you have a build pipeline for each supported branch, the builds most definitely follow versions. Perhaps you are confusing versions with releases?
While there are usual practices and some common sense methods you can expect, it is ultimately up to the software authors and can be whatever they wish, or nothing at all. Neither version nor build numbers are universally used.
In Visual Studio you can set the build number in your project as something similar to a unix timestamp/raw excel date value, so you can convert it back to a date/time of the build.
In that case it would always increment on each build regardless of whatever version numbers you set.