Version Number in Software Version Control

The following are some of the software control knowledge found on the Internet. There is very little information on the Internet in this regard, and it is sent to the blog for anyone who needs it.

The version number consists of two to four parts: the main version number, the minor version number, the internal version number, and the revision number. The primary version and secondary version are required. The version number and revision number are optional. However, the revision number is optional only when the version number is not defined. All defined components must be decimal integers greater than or equal to 0. The metadata limits the main version number, minor version number, internal version number, and revision number to the maximum value of maxvalue-1.

The format of the version number is as follows. Optional components are displayed in square brackets ("[" and:
Main version number. Minor version number [. Internal version number [. revision number]

These parts should be used in accordance with the following conventions:
Major: an assembly with the same name but different major version numbers cannot be exchanged. For example, this applies to a large number of product rewriting, which makes backward compatibility impossible.
Minor: if the names of the two sets are the same as those of the primary version, but the minor version number is different, this indicates a significant enhancement, but takes care of backward compatibility. For example, this applies to the product's revised version or a new version that is fully backward compatible.
Build: different internal version numbers indicate re-Compilation of the same source. This is suitable for changing the processor, platform, or compiler.
Revision: The names, major version numbers, and minor version numbers are the same, but the different revision numbers of the Assembly should be completely interchangeable. This applies to fixing security vulnerabilities in previously released assemblies.
Only subsequent versions of the Assembly with different version numbers or revision numbers are considered to be "quick fix project" (QFE) updates for previous versions. If necessary, you can change the Version Policy in the configuration to make the internal version number and revision number take effect.

Main version or next version
Changes made to the primary or secondary version of the version number indicate incompatible changes. Therefore, version 2.0.0.0 is considered incompatible with version 1.0.0.0. Changing the type of some method parameters or removing a type or method is incompatible.

Internal version
The internal version number is usually used to distinguish between daily versions or compatible versions with minor changes.

Revision No.
Revision number changes are usually reserved for incremental compilation required to fix a specific error. Sometimes you will hear it called the "Urgent error fix", because when it is sent to the customer for fixing a specific error, the change is usually a revision number.
Therefore, an assembly whose compatibility version is 2.0.0.0 is considered incompatible with an assembly whose compatibility version is 1.0.0.0. Similarly, the compatibility version 2.0.2.11 is considered as the QFE of the compatibility version 2.0.2.1.