3.关于版本号基础知识
2012-04-12 19:06
253 查看
A version number is composed of four parts: major number, minor number, build number and revision number,
for example: 14.02.247.005
The first two (major and minor) define what is know as the “public version” of an assembly (notice that this number is used whenever you export an assembly – ex.: COM Interop). The third number defines thebuild
of an assembly. Suppose, for instance, that you work for a company which produces a daily build of an assembly. In this case, this number should beincremented
for each day’s main build. Finally, the last part is called the revision number. You’ll change its value whenever you need to perform an “extra build” to solve a pending issue (ex.: a bug which has beenfound after the daily build).
Now, that we all understand version numbers, I guess I should mention that you’ll encounter several “types” of version numbers. An assembly is always associated with three version numbers:
AssemblyFileVersion: used for information purposes only. It’s the number you see when you access the properties of an assembly in Windows Explorer;
AssemblyInformationalVersion: again, this is used for informational purposes. It indicates the version of the product that includes this assembly.
AssemblyVersion: this version number is stored on the metadata and it’s used by the CLR when binding to strongly named assemblies.
for example: 14.02.247.005
The first two (major and minor) define what is know as the “public version” of an assembly (notice that this number is used whenever you export an assembly – ex.: COM Interop). The third number defines thebuild
of an assembly. Suppose, for instance, that you work for a company which produces a daily build of an assembly. In this case, this number should beincremented
for each day’s main build. Finally, the last part is called the revision number. You’ll change its value whenever you need to perform an “extra build” to solve a pending issue (ex.: a bug which has beenfound after the daily build).
Now, that we all understand version numbers, I guess I should mention that you’ll encounter several “types” of version numbers. An assembly is always associated with three version numbers:
AssemblyFileVersion: used for information purposes only. It’s the number you see when you access the properties of an assembly in Windows Explorer;
AssemblyInformationalVersion: again, this is used for informational purposes. It indicates the version of the product that includes this assembly.
AssemblyVersion: this version number is stored on the metadata and it’s used by the CLR when binding to strongly named assemblies.
相关文章推荐
- 关于笔试题中C++的一些基础知识
- 每一个软件开发人员绝对必须掌握的关于 Unicode 和字符集的最基础的知识
- 关于计算机的基础知识(来自鸟哥的私房菜)
- 关于回调函数和钩子函数基础知识的整理
- C++基础知识—关于默认构造函数的一切
- 关于地图学的一些基础知识
- 【脚本语言系列】关于Python基础知识__slots__,你需要知道的事
- 关于JQuery的基础知识(一)
- 关于学习NDK基础知识这些就够了(五)
- 再探Linux动态链接 -- 关于动态库的基础知识
- 关于studio的build.gradle的基础知识
- 关于“一带一路舆情分析”的基础知识汇总
- 关于继承和覆盖(Override)的一些基础知识
- 【脚本语言系列】关于Python基础知识推导式,你需要知道的事
- 关于回调函数和钩子函数基础知识的整理
- 一些关于空调的基础知识
- 关于mysql基础知识的介绍
- SAR成像基础知识急救箱(二)关于离散傅里叶变换
- 关于WiFi必须了解的基础知识
- 关于学习NDK基础知识这些就够了(二)