Ah, I always close it instinctively. :)
/me who is always shocked by people keeping the two useless right-side
box on their IDE, the server db and the toolbox. That's totally 16
pixels wasted.
M-A
On Wed, Nov 11, 2009 at 11:38 PM, Eric Roman ero...@chromium.org wrote:
Yuck, I experienced the
Thank you! That was it. VS 2008 is now fast and I've switched back.
On Wed, Nov 11, 2009 at 8:38 PM, Eric Roman ero...@chromium.org wrote:
Yuck, I experienced the same gut-wrenchingly slow single stepping problem!
The problem was the Autos view.
VS 2008 conveniently turns this on by
Yuck, I experienced the same gut-wrenchingly slow single stepping problem!
The problem was the Autos view.
VS 2008 conveniently turns this on by default, but it is crazy slow.
Even if it doesn't have focus, it will pause to update it after each step.
Go ahead and right click on Autos and select
On Thu, Oct 29, 2009 at 2:27 PM, Ben Goodger (Google) b...@chromium.orgwrote:
VS2008 builds with /MP by default, and it's well supported, so when present
there's no reason for us to not use it by default. Note that you can still
force VS2005 by setting GYP_MSVS_VERSION=2005 in your
It'd be nice if the defaults could be set on a per-sln level I guess.
-Ben
On Thu, Oct 29, 2009 at 2:30 PM, Peter Kasting pkast...@google.com wrote:
On Thu, Oct 29, 2009 at 2:27 PM, Ben Goodger (Google)
b...@chromium.orgwrote:
VS2008 builds with /MP by default, and it's well supported, so
I've been using VS2008 on Win7 for the last month or so.
I hate it.
Problems:
1) Stepping in the debugger is SOOO slow. I am thinking about going
back to VS2005.
2) If you turn on Intellisense, it crashes like crazy very regularly. I've
turned off intellisense, but it is a big loss in
On Thu, Oct 29, 2009 at 2:38 PM, Mike Belshe mbel...@google.com wrote:
I strongly recommend against VS2008; do others have these problems?
For awhile I was having serious crashiness problems with it. Those stopped,
I don't remember if it was because I installed enough service packs and
It does seem slower, however never having to remember to patch the
appropriate vsprops/gypi with /MP is a big win. When I was ordering the new
machines I found most people on the team I asked were not doing this, and as
a result their builds were 2-3x slower.
-Ben
On Thu, Oct 29, 2009 at 2:38
On Thu, Oct 29, 2009 at 2:38 PM, Mike Belshe mbel...@google.com wrote:
I've been using VS2008 on Win7 for the last month or so.
I hate it.
Problems:
1) Stepping in the debugger is SOOO slow. I am thinking about going
back to VS2005.
I was just about to reply and say the same thing
On Thu, Oct 29, 2009 at 2:38 PM, Mike Belshe mbel...@google.com wrote:
I've been using VS2008 on Win7 for the last month or so.
I hate it.
Problems:
1) Stepping in the debugger is SOOO slow. I am thinking about going
back to VS2005.
2) If you turn on Intellisense, it crashes like crazy
I was just about to reply and say the same thing (on Win 7). It would
take me 2-3 seconds each time I step over a line. I couldn't use it anymore
and switched back to VS 2005.
Isn't the stepping speed affected by things like what you have in your Watch
window and what conditional breakpoints
On Thu, Oct 29, 2009 at 3:23 PM, Finnur Thorarinsson fin...@chromium.orgwrote:
I was just about to reply and say the same thing (on Win 7). It would
take me 2-3 seconds each time I step over a line. I couldn't use it anymore
and switched back to VS 2005.
Isn't the stepping speed affected
From http://dev.chromium.org/developers/how-tos/build-instructions-windows
Ensure that /MP is enabled. You can do this by creating a file called inc
lude.gypi which contains the following lines:
{
'variables': {
'msvs_multi_core_compile': 1
}
}
Put this file in a folder
Yes, this was widely publicized when discovered, yet most people won't make
the change if it's not the default.
-Ben
On Thu, Oct 29, 2009 at 3:42 PM, Jeremy Orlow jor...@chromium.org wrote:
From http://dev.chromium.org/developers/how-tos/build-instructions-windows
Ensure that /MP is enabled.
Here are the fixes for your debugger sluggishness problems:
Bind this macro to F7
http://code.google.com/p/chromium/wiki/WindowsVisualStudioMacros?ts=1256870705updated=WindowsVisualStudioMacros#Only_build_startup_project
and bind this macro to F5
After thinking about it, just setting in Debugging properties:
Command = c:\program files\Debugging Tools for Windows (x86)\windbg.exe
Command Arguments = -o $(TargetPath)
is way simpler, then you just use Ctrl-F5 to start debugging your app!
M-A
On Thu, Oct 29, 2009 at 10:50 PM, Marc-Antoine
On Thu, Oct 29, 2009 at 3:34 PM, John Abd-El-Malek j...@chromium.org wrote:
On Thu, Oct 29, 2009 at 3:23 PM, Finnur Thorarinsson
fin...@chromium.orgwrote:
I was just about to reply and say the same thing (on Win 7). It would
take me 2-3 seconds each time I step over a line. I couldn't
17 matches
Mail list logo
