Hi Bevan,
Yes, I did re-direct the command line output to a log file, now the build
notification emails does not have warnings or errors displayed. Thank you.
Kind regards,
K Bbhavani.
Tel # +91 080 3084 2049
The information contained in this email has been classified:
( ) Larsen & Toubro Limited - General Business
(X) Larsen &Toubro Limited - Internal Use
( ) Larsen &Toubro Limited - Confidential
( ) Larsen & Toubro Limited - Proprietary
From: Bevan Arps [mailto:bevan.a...@clear.net.nz]
Sent: Tuesday, June 11, 2013 12:12 PM
To: Bhavani Kapparmath; nant-users@lists.sourceforge.net
Subject: RE: [NAnt-users] VS2010 devenv command from NAnt fails
Hi Bhavani
I suspect that you'll find those errors are the same as those you see during an
interactive compile.
If you really want to suppress them (I'd put my effort into fixing the
underlying code so it is warning free), redirect the command line output of
devenv.com. The Nant exec task has an attribute for this.
Keep smiling
Bevan.
________________________________
From: Bhavani Kapparmath
Sent: 6/10/2013 7:54 PM
To: bevan.a...@clear.net.nz; nant-users@lists.sourceforge.net
Subject: RE: [NAnt-users] VS2010 devenv command from NAnt fails
Hi Bevan,
After VS2010 build is successful using Nant, I could see whole lot of warning
messages are being displayed/shown in the mail (which is not good) that is sent
from CC.net after build ends.
This was not the case earlier with devenv.exe.
Any idea here? Any thread that has already discussed on this?
Kind regards,
K BBhavani.
Tel # +91 080 6624 3452
The information contained in this email has been classified:
( ) Larsen & Toubro Limited - General Business
(X) Larsen &Toubro Limited - Internal Use
( ) Larsen &Toubro Limited - Confidential
( ) Larsen & Toubro Limited - Proprietary
From: bevan.a...@clear.net.nz [mailto:bevan.a...@clear.net.nz]
Sent: Saturday, May 25, 2013 5:54 AM
To: nant-users@lists.sourceforge.net; Bhavani Kapparmath
Subject: Re: [NAnt-users] VS2010 devenv command from NAnt fails
Devenv.Com is designed for use for batch automation; Devenv.Exe is how the
interactive IDE is launched.
From MSDN:
The devenv.com utility provides for the delivery of output through standard
system streams, such as stdout and stderr, and determines the appropriate I/O
redirection when it captures output, for example, to a .txt file.
I never tried to automate Visual Studio 2005, so it’s possible that using
devenv.EXE worked just fine for that version; for later versions, it doesn’t.
One last thought: Deployment projects are deprecated in Visual Studio 2010 -
and they’re not supported at all by Visual Studio 2012. I’d suggest that you
add some tasks to your product backlog (or equivalent) to migrate away from
.vdproj projects (I’d recommend moving to WiX); once that’s complete
[The entire original message is not included.]
Larsen & Toubro Limited
www.larsentoubro.com
This Email may contain confidential or privileged information for the intended
recipient (s). If you are not the intended recipient, please do not use or
disseminate the information, notify the sender and delete it from your system.
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
