Ok so I kinda solved the problem, but I still do not understand what the hell was going on...
In an effort to make things easier to read, I had put my msbuild parameters on multiple lines, one pair per line (these have paths and are rather long). Apparently ccnet was inserting spaces where linebreaks were found in the config file. Having removed these, ccnet now appears to want to use my msbuild script. What I don't understand is why this was resulting in ccnet "falling- back" to using the solution file, instead of an msbuild error? One of those "poorly understood features" maybe? o.O On Mar 9, 4:06 pm, badfrog <[email protected]> wrote: > Well... more fun. The console won't start, giving an error about not > finding the ccnet.config file in the default location. Which is funny > because ccnet.exe.config has the ccnet.config appsetting that > overrides the default location, and it points to the same location as > ccservice.exe.config. > > The service starts properly however, and I don't see anything in the > event log... > > On Mar 9, 3:46 pm, Ruben Willems <[email protected]> wrote: > > > Hi > > > just an idea : > > stop the service, and start the console : > > do you see any errors, weird logs? > > > with kind regards > > Ruben Willems > > > On Mon, Mar 9, 2009 at 8:44 PM, badfrog <[email protected]> wrote: > > > > Hi all, > > > > We're running v 1.4.0.3524. I have a project that used to have this > > > build task: > > > <msbuild workingDirectory="C:\Path\To\Source"> > > > <executable>C:\WINDOWS\Microsoft.NET\Framework > > > \v3.5\MSBuild.exe</executable> > > > <projectFile>WebService.sln</projectFile> > > > <logger>c:\Program Files\CruiseControl.NET\server > > > \Rodemeyer.MsBuildToCCNet.dll</logger> > > > </msbuild> > > > > I've since changed the configuration (my config file is kept in source > > > control and copied over the existing ccnet.config) to use an msbuild > > > script instead: > > > > <msbuild workingDirectory="C:\Path\To\Source"> > > > <executable>C:\WINDOWS\Microsoft.NET\Framework > > > \v3.5\MSBuild.exe</executable> > > > <projectFile>buildwebsite.proj</projectFile> > > > <targets>Build</targets> > > > <buildArgs> > > > /p:SomeParameters=SomeValues > > > </buildArgs> > > > <logger>c:\Program Files\CruiseControl.NET\server > > > \Rodemeyer.MsBuildToCCNet.dll</logger> > > > </msbuild> > > > > The Project Configuration link on the dashboard shows the correct, > > > updated msbuild task. Whenever I force-build the project, I see an > > > error message referring to WebService.sln -- which no longer exists. > > > CC.NET does not appear to be using my updated build task at all. I've > > > restarted the CruiseControl service on my build server (which in the > > > past has straightened out some of my random config-wont-update issues) > > > but in this case the results are the same, a failure message that > > > refers to the old solution file. > > > > Any ideas?
