DevExpress eXpressApp 框架 (XAF) 和持续集成
我有一个 XAF 应用程序和一个在开发机器上运行良好的 nant 脚本。 该脚本使用 MsBuild 和 .csproj 文件来编译项目。
当 CruiseControl.net 服务器尝试编译项目时，它指出找不到编译所需的 XAF 程序集。
我尝试将 BIN 文件夹中的所有 DLL 引用为本地副本，并尝试在开发服务器上安装 XAF，但没有成功。
有任何想法吗？
I have a XAF application and a nant script that runs fine on the development machines. The script uses MsBuild and the .csproj File to compile the project.
When the CruiseControl.net server tries to compile the project it states that it cannot find the XAF assemblies needed to compile.
I tried referencing all DLLs as Local Copy in the BIN folder and tried installing XAF on the development server, but it hasn't worked.
Any ideas?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您是否尝试过直接在服务器上通过 msbuild 进行构建以确保其正常工作？
当我们部署到 CI 时，我们将使用的 dll 移动到第三方 dll 文件夹并从这里引用它们。 您是否 100% 所有引用都已正确更新，就像添加新模块一样，默认是引用 GAC 中的 dll，这通常没有意义。
我建议不要将 XAF 安装到服务器，因为更新引用的文件夹方法更易于管理，并且如果需要，您可以轻松处理多个分支/版本。
干杯，
克罗克德
have you tried building via msbuild directly on the server to be sure this is working correctly?
When we deployed to our CI we moved the dll´s we used to a thirdparty dll´s folder and referenced them from here. Are you 100% all of your references have been updated correctly as if you add a new module the default is to reference the dll´s in the GAC which usually doesn´t make sense.
I´d advise against installing XAF to the server as if you update the referenced folder approach is easier to manage and you can easily handle multiple branches/ versions if required.
Cheers,
Crocked
当我们在开发服务器上运行自动构建时，我们花了很长时间才获得适合所有内容的准确路径设置。 我们的构建需要 VS6、VS.Net 2003、VS.Net 2005 和 VS.Net 2008。将所有这些环境安装在一台构建机器上会造成一些真正的破坏，试图让所有东西都留在自己的沙子中 -盒子。
最终，使用 Zed 构建和错误，我们能够将每个构建步骤保持在自己的沙子中 -框具有自己的环境变量和自己的注册表设置。
当 nant 编译运行时，您能否获得构建时环境的转储，以查看是否缺少环境变量或指向错误的环境变量？
When we run automated builds on the dev server, it took us a long time to get the exact path settings right for everything. We have builds that require VS6, VS.Net 2003, VS.Net 2005, and VS.Net 2008. Having all of those environments installed on a single build machine made for some real havoc trying to get everything to stay in their own sand-boxes.
Ultimately, using Zed Builds and Bugs we were able to keep each build step silo'd to its own sand-box with its own environment variables, and its own registry settings.
Can you get a dump of what the build-time environment looks like when the nant compile runs to see if there are missing environment variables, or incorrectly pointed environment variables?