我应该如何处理持续集成和 .NET Framework 版本
我刚刚开始转向 .NET Framework 3.5。 我使用 CruiseControl.NET 进行持续集成，并想知道其他人如何进行设置。
我有一个名为 NET3.5 的源代码分支，但现在我将主干保留为 2.0。
我创建了两个 CruiseControl 项目，从主干和分支检出。
因此，即使只有一个代码库，我也有两个持续集成项目。
我认为这是正确的方法，因为我需要使用不同版本的 aspnet_merge.exe 来编译代码，这意味着两个单独的配置文件，因此两个持续集成项目。
这种方法可以吗？每个分支应该单独构建，还是应该只是一个大代码库，在一个巨大的构建中编译不同的发行版本？
干杯
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.
I have a branch of the source code entitled NET3.5 but for now am keeping the trunk as 2.0.
I have created two CruiseControl projects that checkout from the trunk and the branch.
So I have two continuous integration projects even though there is only one code base.
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.
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?
Cheers
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我个人为分支机构创建了一个新的 CCNet 项目，这听起来就像您所做的那样。
这样做的好处是：
当您将分支合并回主干时，然后你可以删除多余的 Cruise 项目。
如果我在这里遗漏了您的 ASP.NET 应用程序的特定内容，请告诉我。
Personally I create a new CCNet project for branches, which sounds like what you've done.
The benefits of this are:
When you merge the branch back into the trunk, then you can remove the extra Cruise project.
Let me know if there's something specific to your ASP.NET application that I've missed here.
切换到 TeamCity 并进行多个构建（每个分支至少一个）。 在 TeamCity 中配置构建非常容易，这绝对是测试不同版本的代码库（包括框架）的正确解决方案。
Switch to TeamCity and have multiple builds (at least one per branch). It's very easy to configure builds in TeamCity, and this is definitely the right solution to testing different versions of your codebase (framework included).