RE: capturing build output in Visual Studio .NET - enabling warning/error double clicking

2005-02-11 Thread Jeff Shanholtz
Thanks! -emacs works great. -Original Message- From: Stefan Bodewig [mailto:[EMAIL PROTECTED] Sent: Friday, February 11, 2005 12:20 AM To: user@ant.apache.org Subject: Re: capturing build output in Visual Studio .NET - enabling warning/error double clicking On Thu, 10 Feb 2005, Jeff

Re: capturing build output in Visual Studio .NET - enabling warning/error double clicking

2005-02-11 Thread Stefan Bodewig
On Thu, 10 Feb 2005, Jeff Shanholtz <[EMAIL PROTECTED]> wrote: > Is there any way I can suppress the "[exec]" part offers a few options. Stefan - To unsubscribe, e-mail: [EMAIL PROTEC

RE: capturing build output in Visual Studio .NET - enabling warning/error double clicking

2005-02-11 Thread sten.rosendahl
ild output in Visual Studio .NET - > enabling warning/error double clicking > > I'm running an ant build script from within VS.NET and capturing the > output in the output window. Right now I am unable to double click an > error or warning line in my build output (which normal

capturing build output in Visual Studio .NET - enabling warning/error double clicking

2005-02-10 Thread Jeff Shanholtz
I'm running an ant build script from within VS.NET and capturing the output in the output window. Right now I am unable to double click an error or warning line in my build output (which normally would open that file to the line with the error/warning). The problem is that VS doesn't understand the