简体繁体 English

多调制应用程序的版本控制

[英]Versioning of multimoduled applications

原文 2013-07-07 18:11:27 2 1 c#/ .net/ module/ unity-container

In a moduled application the main project mainly registers and initializes other modules. 在模块化应用程序中，主项目主要注册并初始化其他模块。 It almost never changes except when new modules are added. 除了添加新模块外，它几乎永远不会改变。 In such cases, version number of the application is not relevant to any of the program's components. 在这种情况下，应用程序的版本号与程序的任何组件都不相关。

In my app (13 modules, C#, .NET 4, unity container) I'm using an xml file to set version number of the product. 在我的应用程序（13个模块，C＃、. NET 4，统一容器）中，我使用xml文件设置产品的版本号。

What are the best practices in versionng of multimoduled products? 在多调制产品的版本管理中有哪些最佳实践？

1 个解决方案

In my experience, the best practices vary depending on the needs of the application or environment. 以我的经验，最佳实践取决于应用程序或环境的需求。

For example, one of our application suites consists of 12 applications comprised of numerous modules. 例如，我们的应用程序套件之一包含12个应用程序，其中包含许多模块。 All of the applications communicate to a central application server using a variety of protocols (.Net Remoting, Web Services, WCF) and from there to a central database. 所有应用程序都使用各种协议（.Net Remoting，Web服务，WCF）与中央应用程序服务器进行通信，然后从该服务器传送到中央数据库。 Because of the high correlation between the database, application server, and applications, they are all on the same major and minor version levels; 由于数据库，应用程序服务器和应用程序之间的高度相关性，它们都处于相同的主要和次要版本级别。 only the revision level is allowed to differ. 仅修订级别允许不同。

However, in scenarios where the correlation is not high, as it sounds like in your application, version matching does not sound nearly as important. 但是，在相关性不高的情况下（听起来像在您的应用程序中一样），版本匹配听起来并不那么重要。 However, there are other considerations to keep in mind such as marketing needs: do you really want to be on version 1 forever even though from a technical standpoint there is no reason to change the version? 但是，还有一些其他需要考虑的因素，例如市场需求：即使从技术角度讲，没有理由更改版本，您是否真的想永远使用版本1？