Is there a way to get VS to stop building my solution on the first error it
encounters?
--
Pete
====
encounters?
--
Pete
====
-
-
Re: Stop on first error
On Oct 3, 1:31 pm, "Peter Morris" <mrpmorri...@SP AMgmail.comwrot e:Hi,Is there a way to get VS to stop building my solution on the first error it
encounters?
>
--
Pete
====http://mrpmorris.blogs pot.comhttp://www.capableobje cts.com
I'm not sure, but IMHO it's better not to, you may get the explanation
of the error in subsequent errors. IIRC when you call a method with
incorrect parameters you get two errors, the first saying than an
overload was not found and the second error says which parameter could
not be converted.
-
Re: Stop on first error
Say I have a solution with 10 projects in. Why would I want the subsequent
9 to fail building when the first one fails? I don't want to see 100
errors, I want to fix the first one. Fixing the first often fixes the
subsequent 99 anyway so I don't feel I am benefiting from the other errors.
Pete
Comment
-
Re: Stop on first error
Pete,
Have you tried using PreBuild-Post Build events ? I haven;t tried yet.
Try using/customising those events.
Thanks
Jibesh
"Peter Morris" <mrpmorrisNO@SP AMgmail.comwrot e in message
news:%23egmv4YJ JHA.1936@TK2MSF TNGP06.phx.gbl. ..Say I have a solution with 10 projects in. Why would I want the
subsequent 9 to fail building when the first one fails? I don't want to
see 100 errors, I want to fix the first one. Fixing the first often fixes
the subsequent 99 anyway so I don't feel I am benefiting from the other
errors.
>
>
Pete
Comment
-
Re: Stop on first error
On Oct 3, 3:28 pm, "Peter Morris" <mrpmorri...@SP AMgmail.comwrot e:Hi,Say I have a solution with 10 projects in. Why would I want the subsequent
9 to fail building when the first one fails? I don't want to see 100
errors, I want to fix the first one. Fixing the first often fixes the
subsequent 99 anyway so I don't feel I am benefiting from the other errors.
>
Pete
We have a solution with 56 projects :)
must of the time when the error is in one of the lower layer projects
you get all the errors in that project and in the other projects you
get at the most that the required dll was not found.
IMHO it's better to just see all the errors, you might have more than
one issue that you can fix at the same time.
Comment
-
Re: Stop on first error
On Fri, 3 Oct 2008 18:31:21 +0100, "Peter Morris"
<mrpmorrisNO@SP AMgmail.comwrot e:
Having used such a compiler in the past, I found it very irritating.>Is there a way to get VS to stop building my solution on the first error it
>encounters?
Having run a compile I could only edit one single error per editing
session, then I would have to compile all over again. With a longer
list of errors I could fix many errors in one editing session before
recomlpiling.
Having said that, may be a parameter that can be set in the IDE so it
will not report more than that many errors. Have a look through the
documentation.
rossum
Comment
-
Re: Stop on first error
But for 1 error I get 20 reports. It's like I'm back in the 80's compiling
COBOL apps from the command line :-)
Comment
Comment