Slow debugging speed in VS2005

[Larry Goldstein]

I have just recompiled several of my large projects under VS2005 and notice
that the speed at which they operate within the Debug configuration has gone
up by a factor of 300-400%. Does anyone know of any settings that I can tweak
(possibly emporarily, say) to get back the former execution speed? Thanks.
--
Larry Goldstein

[Tommy]

If you look at the output window I bet you have a lot of First Chance
Warning's showing up.

Fix those and your speed should go back up. I am having the same issue.

Things like: Dim iVar as Integer = oRow("intfield") will cause a warning.
Casting the row object to integer fixed it for me.

T

"Larry Goldstein" <La************@discussions.microsoft.com> wrote in
message news:B8**********************************@microsof t.com...

I have just recompiled several of my large projects under VS2005 and notice
that the speed at which they operate within the Debug configuration has
gone
up by a factor of 300-400%. Does anyone know of any settings that I can
tweak
(possibly emporarily, say) to get back the former execution speed? Thanks.
--
Larry Goldstein

[Larry Goldstein]

Thanks, Tommy. It must be something like that, but I have absolutely no
warnings whatever. I cleaned up all 250 or so warnings that showed up when I
converted the app. Any other ideas?
--
Larry Goldstein
"Tommy" wrote:

If you look at the output window I bet you have a lot of First Chance
Warning's showing up.

Fix those and your speed should go back up. I am having the same issue.

Things like: Dim iVar as Integer = oRow("intfield") will cause a warning.
Casting the row object to integer fixed it for me.

T

"Larry Goldstein" <La************@discussions.microsoft.com> wrote in
message news:B8**********************************@microsof t.com...

I have just recompiled several of my large projects under VS2005 and notice
that the speed at which they operate within the Debug configuration has
gone
up by a factor of 300-400%. Does anyone know of any settings that I can
tweak
(possibly emporarily, say) to get back the former execution speed? Thanks.
--
Larry Goldstein