Review:
The version number consists of two to four parts:Major, Minor, Build, and Revision numbers。
The major version number and the minor version number are mandatory, the build number and revision number are optional. The revision number section is optional only if the build number section is not defined. All defined components must be decimal integers greater than or equal to 0. The metadata limits the major, minor, build, and revision components to a MaxValue maximum of 1.
The format of the version number is shown below. Optional components are displayed in square brackets ("[" and "]):
Major version number. Version number[.build number[.revision number]]
These sections should be used according to the convention below:
Major: Assemblies with the same name but different major version numbers are not interchangeable. This applies, for example, to a large number of rewrites of products that make it impossible to achieve backward compatibility.
Minor: If both assemblies have the same name and major version number, but different minor version numbers, this indicates significant enhancement, but takes care of backward compatibility. This applies, for example, to a modified version of a product or a new version that is fully backwards compatible.
Build: Different build numbers represent recompilations of the same source. This is suitable for changing processors, platforms, or compilers.
Revision: Assemblies with the same name, major version number, and minor version number, but different revision numbers should be fully interchangeable. This applies to fixing security vulnerabilities in previously released assemblies.
Subsequent versions of an assembly that differ only in build or revision numbers are considered Quick Fix Engineering (QFE) updates to previous versions. If necessary, you can make the build and revision numbers effective by changing the version policy in the configuration.
When building a project, AssemblyInfo1.vb should default to <Assembly: AssemblyVersion("1.0.*")>
After compiling, look at the version information of the dll, you can see that 1.0.1879.26471 is set by yourself, and the third digit 1879 also knows the number of days from 2000.01.01 to the present, so the last digit 26471 is the dynamic control version number.
|
Posted on 10/19/2024 5:12:11 PM
|
|
|
|
