September 26th, 2005More from the â€śwe fix VS.NETâ€? department – in todays episode, weâ€™ll take a
look at the VS.NET debugger and make it faster. Or at least fast enough
so you donâ€™t want to smash your computer waiting for itâ€¦
The steps are ordered by ease of discovering the problem, i.e. a log
of my journey. If you aim for more speed, start at the back and work
your way up instead.
Step 1: Disable all watches and breakpoints you donâ€™t desperately need.
Step 2: Disable â€śEvaluate Expressionsâ€?
Step 3: Set the debugger type.
Set it to â€śNative Onlyâ€? to debug native code, or â€śManaged onlyâ€? if
you have to do managed code. If you absolutely have to debug both, pick
mixed. Under no circumstances leave it set to â€śAutoâ€? – that slows down
debugging tremendously. It seems to take about a second every single
time you step to re-evaluate if this is managed or unmanaged code – and
it doesnâ€™t always get it right.
Step 4: Fix the annoying startup delay
The solution: Add the line
to your lmhosts file in Windows\System32\Drivers\etc
So Say We All!
ColinanymN on Testing Writely for blog … BarryAdede on Testing Writely for blog … MajorLarge on Testing Writely for blog … SammySal on Testing Writely for blog … GlebMut on Testing Writely for blog …
- Attention Reputation
- Cat Meme
- Dog Meme
- Food for Thought
- Influential Thinkers
- Life Long Learning
- Notes to Myself
- Places to Visit
- Ruby on Rails
- Social Entrepreneurship
- Web 2.0
The Glory that was
- 33,473 hits