also, it looks like removing that (to just have normal verbosity) just tells me everything thats going on (in gray text). Nothing else added at end of blue text or what I posed above.
On Fri, Jun 18, 2010 at 3:20 PM, Jon Lumpkin <[email protected]> wrote: > I found that part of it was due to having /v:quiet set, but turning that > on, its still hard to determine what the 'warning' may be > > <msbuild> > > <executable>C:\WINDOWS\Microsoft.NET\Framework\v3.5\MSBuild.exe</executable> > <projectFile>prime.msbuild</projectFile> > <buildArgs>/noconsolelogger /p:Configuration=Debug</buildArgs> > <targets>Build</targets> > <timeout>900</timeout> > <logger>C:\Program > Files\CruiseControl.NET\server\Rodemeyer.MsBuildToCCnet.dll</logger> > </msbuild> > > in prime.msbuild, I do a few things (checkout a new copy of code, etc), > then run > > <MSBuild Projects="$(buildPath)\ReportService.sln" Targets="Rebuild" /> > > Jon > > On Fri, Jun 18, 2010 at 3:02 PM, Dave Johnson <[email protected]>wrote: > >> What does your MSBuild Task block from ccnet.config look like? Can you >> post a snippet? >> >> >> >> Dave >> >> >> ----- Original Message ----- >> From: "Jon Lumpkin" <[email protected]> >> To: "ccnet-user" <[email protected]> >> Sent: Friday, June 18, 2010 1:09:38 PM >> Subject: [ccnet-user] MSBuild Report not showing data >> >> We mainly use MSBuild for all of our builds. I have noticed that when >> you look into the MSBuild Report of a recent build, it doesn't show >> everything. Here is what we are seeing: >> >> Build started >> Project "" (ReportService.BL.csproj target(s)): >> warning CS0168: >> warning CS0649: >> warning CS0649: >> warning CS0649: >> warning CS0649: >> Project "" (ProjectName.vbproj target(s)): >> warning BC40000: >> warning BC40000: >> warning BC42104: >> warning BC42104: >> warning BC42104: >> Build succeeded >> warning CS0168: >> warning CS0649: >> warning CS0649: >> warning CS0649: >> warning CS0649: >> warning BC40000: >> warning BC40000: >> warning BC42104: >> warning BC42104: >> warning BC42104: >> 0 Error(s) >> 10 Warning(s) >> Time elapsed >> >> I am assuming we should be seeing more here, but not sure what is >> wrong. We saw this while running 1.5 RC, as well as the final version. >> > >
