The Insider News - CodeProject

CSharp on the Fritz[^]:
Some time ago, I ran across this conundrum: Why does Visual Studio continue to build projects when a dependent project failed to compile? So, I took it upon myself to figure out how to stop the Visual Studio compiler from building projects unnecessarily. That is: stop building immediately after it encounters an error. My solution took the form of a Visual Studio macro. For the uninitiated: that means writing some Visual Basic code to manage the IDE. For the initiated: You can cringe with me...

Visual Basic to the rescue.

Time spent compiling is never a waste.

Especially since it makes a great legitimate excuse to goof off for a while. Laugh | :laugh:

Never had much issue with VS building things, but then again I've never worked in a huge solution in VS. Eclipse on the other hand...if I haven't been working in Java for a week or so the update and build can take a good 30 mins. Dead | X|

Terrence Dorsey wrote:
Why does Visual Studio continue to build projects when a dependent project failed to compile?

Debugging-purposes in the IDE. I like a list of things that's wrong, not just the first thing that the compiler encountered.

Bastard Programmer from Hell Suspicious | :suss:

If you can't read my code, try converting it here[^]
They hate us for our freedom![^]