Yeah, I thought about that solution but didn't want to pursue it because it
means headaches down the road every time the solution gets updated...
On Tue, Mar 31, 2009 at 13:50, QAH wrote:
>
> I found a quick and dirty temporary solution. Just remove the "Tests"
> folder from the solution. It wi
I found a quick and dirty temporary solution. Just remove the "Tests"
folder from the solution. It will no longer compile it. It only
removes it from the solution, it doesn't delete it. So all you have to
do is add the tests back in when you need them.
On Mar 31, 4:00 pm, Finnur Thorarinsson wro
I think I may have found why this is occurring...
In VS 2005, under Tools \ Options, go to: Projects and Solutions \ Build and
Run
Make sure "Only build startup projects and dependencies on Run" is checked.
For some reason it wasn't checked on my new machine. Maybe it defaults to
being unchecked
It worked for me in the past too - until I switched to my new machine and
sync-ed to latest. :(
>
> On Tue, Mar 31, 2009 at 12:52, Adam Barth wrote:
>
>> On Tue, Mar 31, 2009 at 12:42 PM, Finnur Thorarinsson
>> wrote:
>> > It's not that simple. I think something fishy is going on with our
>> pro
On Tue, Mar 31, 2009 at 12:42 PM, Finnur Thorarinsson
wrote:
> It's not that simple. I think something fishy is going on with our project
> dependencies or something.
Oh, interesting. This has worked for me in the past. (My machine is
really slow and I often skip compiling the tests when I don
It's not that simple. I think something fishy is going on with our project
dependencies or something.
I just setup a new machine last week and when I have Chrome as my startup
project and press F5 it builds no less than 18 (!) projects. Most of which
look like tests. Just look at the list below (d
This isn't how Visual Studio 2005 works for me. Are you sure that the
chrome_exe project is your startup project (i.e., it's bold in the
tree view on the left) and you're pressing F5 (and not F7 or
Shift-F7)?
Adam
On Tue, Mar 31, 2009 at 12:34 PM, QAH wrote:
>
> When I do that, it still reach
When I do that, it still reaches into the "unit_tests" subproject and
tries to compile that code. I don't want it to do that because it
gives me lots of errors from the unit tests.
On Mar 31, 3:30 pm, Adam Barth wrote:
> Set chrome_exe as your startup project and press F5!
>
> Adam
>
>
>
> On Tu
Set chrome_exe as your startup project and press F5!
Adam
On Tue, Mar 31, 2009 at 12:14 PM, QAH wrote:
>
> Hello everyone! I got google chrome to compile, but there were lots of
> errors given to me with the unit tests. The browser can still run
> without the tests, so how can I stop the unit
