Stops a solution build immediately after a project has failed to build.

(23) Review
Visual Studio
2013, 2012, 2010, 14
Download (26,725)
E-mail Twitter Digg Facebook
Add to favorites
Reviews (23)
Q and A (1)
Sign in to write a review
Sort by:

by Solomon Rutzky | February 18 2015

by fantastroy | October 10 2014

hmm it does not work for my ultimate visual studio 2013 C++ project

by KyronSr | June 13 2014

Very simply and does what it says it does. I have a 90 project solution and this has helped a lot with catching problems.

by Believe2014 | June 11 2014


by Duane Newman | June 04 2014

Very useful tool when I'm dealing with larger solutions, get's me fixing issues sooner rather than later.

by VincentS | May 21 2014

by Sergii Volchkov | March 27 2014


by Amid | November 11 2013

Neat tool. Especially useful for 100+ projects solution.

by Andrei_Fedarets | October 24 2013

So simple, but very helpful :)

by Mohammad Azis Fatoni | September 24 2013

by Laurent Berthet | June 17 2013

by Mystcreater | November 26 2012

Very nice extension. After Microsoft have been removed the macros in Visual Studio 2012, I was bored to don't have this feature. When you have a big solution with many projects, it help to don't have to wait before the entire process even if your firsts projects failed.

Thank you again!

by Karel Kral | November 07 2012

by .daryn | June 15 2012

Faster turnaround in my work. So easy. Nice.

The Build menu check option is a nice touch.

by André Luus | May 25 2012

Works like a charm! Thanks so much.

by GBelzile | April 25 2012

You made my day!

by vanslyck | March 08 2012

When working on solutions that contain 50+ projects, this saves us a lot of time. Thank you for making such a useful plug-in.

by Eric Harding | December 07 2011

by cportwood | October 13 2011

I love this addon. My only criticisim is it defaults to being checked. It would be nice if there were some settings to allow it to be easier to use. I rarely want it on a rebuild and it would be nice to be a seperate build button on the toolbar instead of a checkbox. It does perform well and does not seem to have any problems with memory leaks or conflicts with other extentions. All in all it is a great extention. It would be perfect with a few small updates.

by JC Oldridge | July 18 2011

Saves lots of lost time every week, works great.

1 - 20 of 23 Items   
Sign in to start a discussion

  • Doesn't work for Visual studio 2012
    9 Posts | Last post Wed 8:48 PM
    • the "Stop Build on first error" option doesn't show up after I installed it.
      Have tried to reinstall.
    • Hi
      I haven't heard of that happening before. I'm running it myself on VS2012 without problems. What service pack of VS are you on?
    • I was having this problem in VS2013.  I fixed it by searching ("Quick Launch" in the upper right hand corner) for "Stop On First Build Error."  Then I toggled both the options from False to True.  After that, the options appeared in my Build menu, and didn't disappear when I unchecked them.
    • I installed on a VS 2013 Ultimate edition and it does not work. It kept compiling after the first error. I thought it was suppose to stop. (And yes I do have the Stop on First error selected in the build menu).
    • Hi Peter
      Doesn't it stop at all? Also, despite the name it doesn't stop immediately on first error, it stops after the first project has failed, i.e. it doesn't try to build additional projects after one has failed. Does it try to build all projects for you, even with the "Stop on first build error" option checked?
    • Yes it compiles through multiple projects -- does not stop after first project fails. Sorry for being unclear.
    • I just installed the latest version into VS 2012 and it no longer loads.  I've tried uninstalling it and re-installing it.  Is there anywhere to download the previous version?
    • @Michael: Sorry, I don't have VS2012 anymore to test on. I built it with VS2013 and it insisted on updating the project. I don't think the Visual Studio Gallery allows you to download older versions. Probably the only thing you can do is get the source code and build it yourself against the VS2012 extension kit.
    • Version 1.7 that I just released should support VS2010 and VS2012 properly again.