问题描述
我刚刚开始移动到.NET Framework 3.5。我使用CruiseControl.NET为我们的持续集成，并想知道其他人进场设置此功能。
I am just beginning the move to the .NET Framework 3.5. I use CruiseControl.NET for our Continuous Integration and would like to know how other people approach setting this up.
我的源$ C $ C分行有权NET3.5但现在我保持躯干为2.0。
I have a branch of the source code entitled NET3.5 but for now am keeping the trunk as 2.0.
我已经创建了一个从主干和分支检出2 CruiseControl的项目。
I have created two CruiseControl projects that checkout from the trunk and the branch.
所以，我有两个连续的集成项目，即使只有一个code碱基。
So I have two continuous integration projects even though there is only one code base.
我认为这是正确的做法，因为我需要使用不同版本的aspnet_merge.exe的编译code，这意味着两个不同的配置文件，从而在两个连续的集成项目。
I think this is the correct approach because I need to use different versions of the aspnet_merge.exe to compile the code which means two separate configuration files and thus the two continuous integration projects.
这是正常的做法，应该每个分支单独构建，还是应该仅仅是一个大code表示编译不同发布版本中一个巨大的建基地？
Is this approach OK, should each branch be built separately or should it just be one big code base that compiles different release versions in one giant build?
干杯
推荐答案
我个人创建一个新的CCNET项目的分支，这听起来像你做了什么。
Personally I create a new CCNet project for branches, which sounds like what you've done.
这样做的好处是：
- 在改变一个分支只会导致一个项目来重建
- 您必须单独建立报告/工件的每个分支
- 如果一个分支断裂，仍然可以建立另一个分支/部署
在合并分支到主干，那么你就可以删除多余的游船项目。
When you merge the branch back into the trunk, then you can remove the extra Cruise project.
让我知道，如果有具体的东西，你的ASP.NET应用程序，我已经在这里错过了。
Let me know if there's something specific to your ASP.NET application that I've missed here.
这篇关于我应该如何处理持续集成和.NET Framework版本的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！