问题描述
MSDN文档：
我的问题是关于意的条款建立和修改在这方面。
在我看来，在一般的说法，我们做的构建，当有变化的来源中。因此，建设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:
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?
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建立与修订的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！