I guess I won't be using the parallel option in Visual Studio, then. A non-deterministic build order is not worth the risk.<br><br>Juan<br><br><div class="gmail_quote">On Thu, Jul 30, 2009 at 10:53 AM, John Drescher <span dir="ltr"><<a href="mailto:drescherjm@gmail.com">drescherjm@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5">On Thu, Jul 30, 2009 at 11:44 AM, j s<<a href="mailto:j.s4403@gmail.com">j.s4403@gmail.com</a>> wrote:<br>
> By default visual studio uses 2 threads on my machine, a dual core AMD.<br>
><br>
> I notice when I have RUNTESTS (I can't remember) enabled, it may attempt to<br>
> run the tests before my project is even built.<br>
><br>
> If certain sub directories depend on a target in another directory already<br>
> being built, is it safe to use the multi-threaded option in visual studio?<br>
><br>
<br>
</div></div>I have been using parallel builds with visual studio 2005 for over 1<br>
year. It sometimes creates situations like this but since it saves me<br>
10s of minutes per day I deal with the issues. Generally building the<br>
same project a second time fixes any problems and is usually quick<br>
since most stuff builds correctly on the first pas.<br>
<font color="#888888"><br>
John<br>
</font></blockquote></div><br>