Hi
for the msbuild, you can lower the verbosity of msbuild :
In the docs it says for the buildargds of msbuild:
<buildArgs>/noconsolelogger /p:Configuration=Debug /v:diag</buildArgs>
this is the help of msbuild
/verbosity:<level> Display this amount of information in the event log.
The available verbosity levels are: q[uiet], m[inimal],
n[ormal], d[etailed], and diag[nostic]. (Short form: /v)
Example:
/verbosity:quiet
so you can set it /v:diag to /v:n or so
with kind regards
Ruben Willems
On Thu, Aug 28, 2008 at 3:54 PM, Susan Gorman
<[EMAIL PROTECTED]>wrote:
> When CVS tags my source code, the list of every single dang file it is
> tagging gets written out to ccnet.log, really bloating the log file. For
> example…
>
>
>
> 8/28/2008 3:58:02 AM: [MyProject:Warning]: Source control wrote output to
> stderr: cvs server: Tagging .
>
> cvs server: Tagging docs
>
> cvs server: Tagging docs/Docs4SQA
>
> cvs server: Tagging docs/Docs4SQA/AV
>
> cvs server: Tagging docs/Docs4SQA/Max
>
> ad nauseum
>
>
>
> Is there a way to prevent CVS tagging from going to the log without losing
> **all** warnings?
>
>
>
> On a related note, I have an msbuild task where the entire output from
> msbuild is getting written to the ccnet.log file. Again, is there a
> control/attribute that would prevent something from getting written to
> ccnet.log?
>
>
>
> Thank you,
>
>
>
> *Susan Gorman*
>
> *CM Team Lead*
>
> *Install Developer*
>
>
>
> Sunbelt Software
>
> 33 N. Garden Ave. #1200
>
> Clearwater, FL 33756
>
> 727-562-0101
>
>
>
>
>
