Why is Build Fails with CruiseControl.NET, but it builds fine manually with the same settings?

Question

I have a project that builds great. If I create it manually, but it does not work with CC.NET.

The error that appears on CC.NET is mainly due to the fact that the import was unsuccessful because the file was not found; one of the projects (C ++ dll) is trying to import a dll built by another project. The dll should be in the right place, because there is a dependency between projects - indeeed, when I build manually, everything works fine (note that when I speak manually, I get everything fresh from the source code repository, and then calling Rebuild from VS2005 to simulate CC.NET Automation).

it looks like dependencies are ignored when the assembly is automated through CC.NET.

I am creating a Release MinDependency mode.

Any help would be greatly appreciated!

Answer 1

Can you change CC to use msbuild instead of devenv? This seems like the best solution for me, as it means that the assembly is the same in both situations.

Answer 2

After a long investigation - my understanding of this at this stage is that the problem is that I use devenv to create through CruiseControl.NET, but when I create it manually, VisualStudio uses msbuild.

This basically leads to ignoring the dependencies (due to some msbuild arg command that I don't play using devenv).

, , ++, , CC.NET .NET- ++.

, .

.

Answer 3

, .

Answer 4

, , , / , . , CruiseControl ( MSBuild), . , MSBuild CruiseControl, , MSBuild (2.0) ++ sln Visual Studio . MSBuild ++-, v3.5, ++-.

Answer 5

, CC.Net , .

- CC.Net , DLL ? ? ? CC.Net , .

Answer 6

, , IDE , , ( msbuild, devenv.) reference - , , . , IDE, VisualStudio . , ( .)

/ , .

Answer 7

, , , CC.NET . , ++ . lib include, → → → V++. , , .

, (BuildUser) . BuildUser . , CC.NET BuildUser .

Answer 8

(reposting, , , )

VC2003, , .

:

• ProjectA → A.lib
• ProjectB → B.exe
  • → Linker → , A.lib .
  • ProjectA ( ).

ProjectB, A.lib ProjectB. , .

CC.NET , , A.lib .