FIX: Slow debugging in Visual Studio 2005

[neufuse Veteran]

I know some of you have seen this problem. Stepping through code in the

debugger is slow as heck in Visual Studio 2005. Well here is the problem,

Edit and continue. Because edit and continue does run time compileing of

code as it executes, it causes a big slow down in execution time. To disable

this and return the debugger to the normal speed as it was in VS.NET 2003,

do the following.

Go to tools menu > options

Select debugging form the left tree expand it

click on Edit and Continue in the list.

Uncheck "Enable edit and continue"

rebuild your project and step through code, it should be fast as VS.NET 2003

was now.

[+Biscuits Brown MVC]

We havent seen any difference in debugging speeds here. It could be perhaps because our apps are not that large thus the compile isn't long enough for it to matter. Even so, I think I would would rather have edit and continue on and a slower debug than to completely disdable edit and continue.

[neufuse Veteran]

  Tempus said:

We havent seen any difference in debugging speeds here. It could be perhaps because our apps are not that large thus the compile isn't long enough for it to matter.  Even so, I think I would would rather have edit and continue on and a slower debug than to completely disdable edit and continue.

586792338[/snapback]

trust me, you wouldn't...

20 seconds to step from one line to the next...

[idbuythatforadollar]

i've never had that problem, are you working with 20,000 line procedures or something stupid?

[Computer Guru]

why 'somethign stupid'?

i have a 6000 line procedure that is as optimized as its going to get without a complete rewrite, and i have the same thing, except its about 1-2 seconds or so.

what kind of machine are you running it on? .NET takes advantage of SSEX optimizations.

[Malisk]

Procedures not split up is sometimes called "stupid" because they get hard to get an overview of.

It doesn't have anything to do with optimization, it has to do with splitting up your work and modularizing.

[elliot]

  Quote

Because edit and continue does run time compileing of code as it executes, it causes a big slow down in execution time.

Edit and continue *does not* compile the code as you step through it.

When you make an edit the program is updated in memory, if you don't make any edits then there's no reason why edit and continue would slow you down.

Look here for more info

http://msdn.microsoft.com/library/default....it_continue.asp

[neufuse Veteran]

  idbuythatforadollar said:

i've never had that problem, are you working with 20,000 line procedures or something stupid?

586804580[/snapback]

what are you talking about? I work with programs that are in the 500,000 line range with all the business logic we deal with

[neufuse Veteran]

  elliot said:

Edit and continue *does not* compile the code as you step through it.

When you make an edit the program is updated in memory, if you don't make any edits then there's no reason why edit and continue would slow you down.

Look here for more info

http://msdn.microsoft.com/library/default....it_continue.asp

586814286[/snapback]

MS has confirmed on their bug reporting site what I stated was the cause is the cause in the RTM build, constant in memory compiling... its not necessarly from changing code but other things it does at runtime with the compiler services

[neufuse Veteran]

  Quote

what kind of machine are you running it on? .NET takes advantage of SSEX optimizations.

586804963[/snapback]

My dev machine is a dual Xeon system at 3.4GHz with 4GB RAM and RAID0 10K RPM hard drives... so speed isn't the issue there

[di ana]

  neufuse said:

I know some of you have seen this problem. Stepping through code in the

debugger is slow as heck in Visual Studio 2005. Well here is the problem,

Edit and continue. Because edit and continue does run time compileing of

code as it executes, it causes a big slow down in execution time. To disable

this and return the debugger to the normal speed as it was in VS.NET 2003,

do the following.

Go to tools menu > options

Select debugging form the left tree expand it

click on Edit and Continue in the list.

Uncheck "Enable edit and continue"

rebuild your project and step through code, it should be fast as VS.NET 2003

was now.

That solved it, thank you