I am using web apps (with 'Enable Edit and Continue' enabled) , and I STILL have the same issue .....
Can the issue also exist with something else enabled?
FYI I noticed this after i uninstalled resharper.
FYI I reset all the defaults too.
Quite off topic:
I signed up to this site to post on this message , but isnt the password requirements OVERKILL: Invalid password. All passwords must be at least 8 characters long and contain at least 1 uppercase character, a lowercase character, a numeric character (digit), and a special character.
Just to make sure, you have the _project_ option enaebled right? (not the Tools->Options->Debugging option).
I am not sure why the project system might still tell the debugger to detach with this option enabled. My only suggestion would be to use Terminate All instead of Stop Debugging.
Gregg
Gregg Miskelly
Visual Studio Debugger Dev
http://blogs.msdn.com/greggm/
The solution is to do Terminate All instead of hitting stop You need to add this option to your toolbar.
To do so:Right click on the toolbar, click Customise... In the left pane choose
Debug. In the right pane scroll down until you see Debug All. drag it to your toolbar and click in when you want the code to
really stop executing.
I too have had this issue and it drives me mad. Yes, you can use Debug - Terminate all to prevent it from happening, but then it takes ages to start again.
Microsoft - please ask yourself why on earth you wrote the debugger this way. I can't think of anyone who would rather the remainder of the code executes when you click stop - if you'd have wanted that you would have run it yourself. It's such a shame to
see a great development environment marred by such ridiculous features - who on earth came up with that idea? It's like your car continuing to the end of the road when you hit the break pedal.
The ability to stop code needs to be a separate option from 'Enable Edit and Continue', and it needs to be available to web applications too.
uberginsu
Member
2 Points
1 Post
Re: Stop Debugging Command Doesn't Stop Execution
Feb 19, 2008 06:33 PM|LINK
I am using web apps (with 'Enable Edit and Continue' enabled) , and I STILL have the same issue .....
Can the issue also exist with something else enabled?
FYI I noticed this after i uninstalled resharper.
FYI I reset all the defaults too.
Quite off topic:
I signed up to this site to post on this message , but isnt the password requirements OVERKILL:
Invalid password. All passwords must be at least 8 characters long and contain at least 1 uppercase character, a lowercase character, a numeric character (digit), and a special character.
greggm
Member
58 Points
11 Posts
Re: Stop Debugging Command Doesn't Stop Execution
Feb 19, 2008 08:09 PM|LINK
Just to make sure, you have the _project_ option enaebled right? (not the Tools->Options->Debugging option).
I am not sure why the project system might still tell the debugger to detach with this option enabled. My only suggestion would be to use Terminate All instead of Stop Debugging.
Gregg
Visual Studio Debugger Dev
http://blogs.msdn.com/greggm/
BossDida
Member
18 Points
22 Posts
Re: Stop Debugging Command Doesn't Stop Execution
Jun 11, 2009 08:20 PM|LINK
Hi all,
I have the same problem too.
Is it a bug or it's supposed to be in this way and is there any solution or workaround of this issue ?
Thanks in advance.
adinas
Member
15 Points
9 Posts
Re: Stop Debugging Command Doesn't Stop Execution
Jun 12, 2009 12:19 PM|LINK
The solution is to do Terminate All instead of hitting stop You need to add this option to your toolbar.
To do so:Right click on the toolbar, click Customise... In the left pane choose Debug. In the right pane scroll down until you see Debug All. drag it to your toolbar and click in when you want the code to really stop executing.
andyrwebman
Member
4 Points
22 Posts
Re: Stop Debugging Command Doesn't Stop Execution
Jul 06, 2011 03:17 PM|LINK
I too have had this issue and it drives me mad. Yes, you can use Debug - Terminate all to prevent it from happening, but then it takes ages to start again.
Microsoft - please ask yourself why on earth you wrote the debugger this way. I can't think of anyone who would rather the remainder of the code executes when you click stop - if you'd have wanted that you would have run it yourself. It's such a shame to see a great development environment marred by such ridiculous features - who on earth came up with that idea? It's like your car continuing to the end of the road when you hit the break pedal.
The ability to stop code needs to be a separate option from 'Enable Edit and Continue', and it needs to be available to web applications too.