Strange Debugger issues

[cduden]

Not sure which group this question would go in so if this isn't the
appropriate place I apologize.

Here is the setup --

Rather large project consisting of a Winform client that communicates with a
series of SAO, Single Call, IIS hosted remoted facades all written in C#.

Up until recently everything was working just fine, I could debug both the
client and server components. Now when I debug into the server components I
can set one or more breakpoints and it will hit the breakpoint just fine.
If I use F5 I can run to the next breakpoint most of the time. What I can't
do is step through the code (F10 or F11), doing so may work for a line or
two (or not) but inevitably it will lock up the IDE and everything goes into
the abyss from there. When this happens, even after letting it sit and run
for half an hour, the only way out is to kill IIS and the client app. Many
times this causes Visual Studio to crash and restart. I have no problems
debugging through the client code at all. The application runs fine when
the debugger isn't attached.

Does anyone have any insight into this strange phenomena?

Thanks,
CMD

[cduden]

Nevermind -- I have been having problems with this for 2 days and after
posting the message I deleted all the compiled dlls and pdbs accross all the
projects rebuilt everything and suddenly it works. Interestingly I had the
same symptoms on multiple machines.
"cduden" <cd****@netfusionservices.com> wrote in message
news:uA**************@TK2MSFTNGP15.phx.gbl...

Not sure which group this question would go in so if this isn't the
appropriate place I apologize.

Here is the setup --

Rather large project consisting of a Winform client that communicates with a series of SAO, Single Call, IIS hosted remoted facades all written in C#.

Up until recently everything was working just fine, I could debug both the
client and server components. Now when I debug into the server components I can set one or more breakpoints and it will hit the breakpoint just fine.
If I use F5 I can run to the next breakpoint most of the time. What I can't do is step through the code (F10 or F11), doing so may work for a line or
two (or not) but inevitably it will lock up the IDE and everything goes into the abyss from there. When this happens, even after letting it sit and run for half an hour, the only way out is to kill IIS and the client app. Many times this causes Visual Studio to crash and restart. I have no problems
debugging through the client code at all. The application runs fine when
the debugger isn't attached.

Does anyone have any insight into this strange phenomena?

Thanks,
CMD