CruiseControl.NET 和 Visual Studio 异步 CTP
我已签署一项为我们的项目设置 CruiseControl.NET 的任务。一切都很顺利，直到我意识到我们正在使用异步 CTP。我的问题如下：
- 除了通过 Visual Studio 之外，还有其他调用异步 CTP 构建机器的选项吗？ （不使用VS手动进行预处理。）
- 如何强制CruiseControl.NET使用Async CTP构建项目？
I have been signed a task to set up CruiseControl.NET for our project. Everything went fine until I stomped on the fact that we were using Async CTP. My questions are following:
- Are there any options for calling Async CTP build machine other than through Visual Studio? (Do the preprocessing manually without using VS.)
- How to force CruiseControl.NET to build a project with Async CTP?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
对我有用的技巧是从我安装了带有 async ctp 的 VS 的电脑中获取 msbuild，并替换构建服务器上构建机器上的 msbuild。
The trick that worked for me was to take the msbuild from my pc where I had VS with async ctp installed and replace the msbuild on the build machine at the build server.
我不熟悉 Cruise Control .NET，但熟悉异步 CTP 的工作原理。
CTP 包括支持 CTP 的编译器。您应该能够在构建计算机上安装CTP，这将允许它编译异步.NET 代码。
如果 CTP 安装程序需要 Visual Studio，则您应该能够安装 VS，然后安装 CTP，然后卸载 VS，同时仍然在计算机上保留支持 CTP 的编译器。
这类似于我期望有人将 CTP 与 ASP.NET 的按需编译方案结合使用。
I'm not familiar with Cruise Control .NET, but I'm familiar with how the Async CTP works.
The CTP includes an CTP-capable compiler. You should be able to install the CTP on your build machine, which will allow for it to compile Async .NET code.
If the CTP installer requires Visual Studio, you should be able to install VS, then the CTP, and then uninstall VS while still leaving a CTP-capable compiler on your machine.
This is similar to how I would expect someone to use the CTP in conjunection with compile-on-demand scenarios for ASP.NET.
我使用另一个构建服务器工具 TeamCity，但由于这一切都归结为 MSBuild，我认为它应该工作相同。
我对与 Async CTP 的兼容性也有同样的疑问，因为它向 .NET 本身添加了关键字，但在尝试之后，似乎您需要做的就是在项目中引用 AsyncCtpLibrary.dll，并确保DLL 到达您的构建服务器。我建议将其包含在您的版本控制系统中，例如。 Subversion，因此引用是相对于您的项目根目录的，并且将自动位于构建服务器上的正确位置。
这样您就不必“欺骗”您的计算机来安装完整的软件包。
I use another build server tool, TeamCity, but since it all comes down to MSBuild, I think it should work the same.
I had the same doubts about the compatibility with the Async CTP, since it adds keywords to .NET itself, but after trying it, it seems that all you need to do is reference the AsyncCtpLibrary.dll in your project, and make sure that the DLL gets to your build server. I suggest including it in your version control system, ex. Subversion, so the reference is relative to your project root and will automatically be at the right place on your build server.
This way you don't have to "trick" your computer to install the full package.