净AssemblyName.version建立与修订 [英] .Net AssemblyName.version Build versus Revision
问题描述
MSDN文档：
版号码包括二至四个 成分：主要，次要，构建和 修订。主要的和次要的 组件是必需的;构建和 修正组件是可选的，但 如果构建组件是必需的 修订分量定义。所有 定义的组件必须是整数 大于或等于0。
的版本号的格式为 如下（任选组分示 在方括号（[和]）： 为major.minor [.build [.revision]的 部件所使用的约定 如下：
专业：大会具有相同名称 但不同的主要版本是不 互换。更高版本 数量可能表明一个重大的重写 一个产品的，其中后向 兼容性不能假设
小：如果名称和主要 上两个组件版本号是 相同的，但次要版本号 是不同的，这表示 显著增强与 有意向后兼容。 这种更高的次要版本可能数 指示的产品的点释放 或完全向后兼容的新 版本的产品。
生成：在版本号的差异 再presents相同的重新编译 资源。不同的构建数字可能 被用于在处理器，平台， 或编译器的变化。
修订：大会具有相同 名，主要和次要版本号 但不同版本的目的 是完全可互换。较高 版本号可能会在使用 建设，修复安全漏洞的 previously发布组装。
随后装配的版本 仅相差建立或修订 号被认为是修补 之前版本的更新。
我的问题是关于意的条款建立和修改在这方面。
在我看来，在一般的说法，我们做的构建，当有变化的来源中。因此，建设678和建设679是不同的 precisely 的，因为来源是在某些方面不同 - 通常是由于一些改变源签的结果。在我看来，该.NET定义使用修订于一体普遍采用建的方式。
是否有人使用上述定义他们的版本？如果是这样，你能给你为什么具体的例子吗？
组装仅相差版本或修订号后续版本被认为是先前版本的修补程序更新。
本节介绍的差异。该修订时使用你的产品已经售出，你需要做出修正到出厂版本，而你已经有更新的进展。
例如1.1.10.0船舶。我作出小的修改功能，并感到在1.1.20.0当我需要确定一个安全警报。我不能增加1.1.10.0至1.1.11.0，作为重presents别的东西。所以我用1.1.10.1，以确定它是1.1.10.0 code修订。
希望这是比泥更清楚一点。还记得该公司的那想出了这些定义的尺寸和软件项目他们船舶的大小
The MSDN documentation states:
Version numbers consist of two to four components: major, minor, build, and revision. The major and minor components are required; the build and revision components are optional, but the build component is required if the revision component is defined. All defined components must be integers greater than or equal to 0.
The format of the version number is as follows (optional components are shown in square brackets ([ and ]): major.minor[.build[.revision]] The components are used by convention as follows:
Major: Assemblies with the same name but different major versions are not interchangeable. A higher version number might indicate a major rewrite of a product where backward compatibility cannot be assumed.
Minor: If the name and major version number on two assemblies are the same, but the minor version number is different, this indicates significant enhancement with the intention of backward compatibility. This higher minor version number might indicate a point release of a product or a fully backward-compatible new version of a product.
Build: A difference in build number represents a recompilation of the same source. Different build numbers might be used when the processor, platform, or compiler changes.
Revision: Assemblies with the same name, major, and minor version numbers but different revisions are intended to be fully interchangeable. A higher revision number might be used in a build that fixes a security hole in a previously released assembly.
Subsequent versions of an assembly that differ only by build or revision numbers are considered to be Hotfix updates of the prior version.
My question is concerning the meaning of the terms Build and Revision in this context.
It seems to me that in general parlance, we do "builds" when there are changes in the source. Thus "build 678" and "build 679" are different precisely because the sources are different in some way - typically as a result of a checkin of some changed source. It seems to me that the .NET definition uses "Revision" in the way one generally uses "build".
Does anybody USE the definition above in their versioning? If so can you give concrete examples of WHY you did?
Subsequent versions of an assembly that differ only by build or revision numbers are considered to be Hotfix updates of the prior version.
This section explains the difference. The Revision is used when your product has shipped and you need to make fixes to a shipped version while you are already progressing with updates.
For example 1.1.10.0 ships. I am making small changes to functionality and am at 1.1.20.0 when I get a security alert that needs fixing. I can't increment 1.1.10.0 to 1.1.11.0, as that represents something else. So I use 1.1.10.1 to identify it is a revision of the 1.1.10.0 code.
Hope this is a little clearer than mud. Also remember the size of the company and the size of the software projects they ship that came up with these definitions.
这篇关于净AssemblyName.version建立与修订的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
