Can you post the <devenv> section of your ccnet.config file to this list?
Kind regards, Tim -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of John_Idol Sent: 12 November 2008 09:12 To: ccnet-user Subject: [ccnet-user] Re: Why Build Fails with CruiseControl.NET but it builds fine manually with same settings? Thanks. I am using devenv. - Environment variables are fine (I am building manually with same user the service is registered to). - Project Build order is fine (If I remove a dependency between the project that looks for the dll and the project that generates this dll build order is wrong and I cannot build manually - adding this dependency fixed build order and manually it runs fine). - Dlls are being built to a central folder called "Output" (dll that's missing is there when building manually it is not when it fails through CC.NET) - My service account is the same that I use to build manually (and I can create stuff etc.) How do I build manually using devenv? (never done this) Suppose is something like devenv "solutionName.sln" "buildMode" ... Cheers On Nov 12, 9:06 am, "Tim Rayment" <[EMAIL PROTECTED]> wrote: > How are you building the solution with CruiseControl? Are you using the > MSBuild task or the devenv task? > Have you tried building from the command line without using CC. > Other things to check would be: > Environment variables > Project build order > Find out where the dlls are being built to > Check that your service account has permissions to copy files to the > output folder > > Kind regards, > > Tim > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On > > Behalf Of John_Idol > Sent: 12 November 2008 08:49 > To: ccnet-user > Subject: [ccnet-user] Re: Why Build Fails with CruiseControl.NET but it > builds fine manually with same settings? > > HI Ruben - thanks for helping. > > What do you mean with "reference path", do you mean the reference for > the not found dll on the proejct that looks for it? > It is pointing with an import to an output folder where the other > project is supposed to copy on post build the dll. If running with > CC.NET service dll is not in this output folder - if manually It is > there (so it doesn't fail). > > I will try to debug the problem using the console app instead of the > service. > > Any other idea? > > On Nov 12, 7:17 am, "Ruben Willems" <[EMAIL PROTECTED]> wrote: > > Hi > > > can you check the project file manually? > > --> open it in notepad or so, and check the reference path > > > I've seen in many cases that VS can compile a solution, but msbuild does > > not. > > and in all these cases, there was a wrong path in the project file. > > > with kind regards > > Ruben Willems > > > On Tue, Nov 11, 2008 at 10:23 PM, John_Idol > <[EMAIL PROTECTED]>wrote: > > > > I have a project that builds fine If I build it manually but it fails > > > with CC.NET. > > > > This project is composed by a number of .NET projects and a few C++ > > > dlls. > > > > The error that shows up on CC.NET is basically related to an import > > > that's failing because file was not found; one of the projects (C++ > > > dll) tries to import a dll built by another project. Dll should be in > > > the right place since there's a dependency between the projects - > > > indeed when I build manually everything works fine (Note that when I > > > say manually I am getting everything fresh from source code repository > > > then invoking a Rebuild from VS2005 to simulate CC.NET automation). > > > When I run through CC.NET though the dll is not in the right place (I > > > checked after the build failed and it was not physically in the > > > folder). > > > > Looks like dependencies are ignored when the build is automated > > > through CC.NET. > > > > I am building in Release MinDependency mode. > > > > Any help would be highly appreciated!
