|
Hi,
I have several VB projects I currently work on and recently whilst debugging the development server just stops. The applications continue to run and there are no errors. I'm using the Visual Studio Development server when debugging. Is there a setting I'm missing that sets how long the dev server is allowed to run for, it currently seems to be about 1 minute?
Thanks
Nick | | NickMaz Monday, October 05, 2009 8:08 AM | Hello Nick, What do you mean "the development server just stops", does it say the debugger hang there or the IDE is unresponsive? Did we install the latest version of Visual Studio (SP1)? Please try to installe the latest hotfix of SP1: http://support.microsoft.com/kb/967631/en-usBesides, please go to Tools -> Options -> Debugging -> General and check "Enable Just My Code" option. This will automatically unenable the source server support. If we enable the source server support, it may take a few seconds for Visual Studio to download the symbols. Best regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have any feedback, please tell us.
Welcome to the All-In-One Code Framework! | | Roahn Luo Tuesday, October 06, 2009 3:59 AM | Hi, I'll try to explain, I will run an application to debug setting some breakpoints, all the 'step into', step over' functions etc work for about a minute then the debugger will just stop. Normally during debugging the Start Debugging Icon is disabled whereas the Break All & Stop Debugging icons are enabled. This is the case for about 1 minute then when debugging stops the Start Debugging icon becomes enabled and the other 2 disabled. The application will continue to run but will not break on any of the breakpoints, therefore I cannot debug. The hotfix scenarios don't seem to match what is happening and the option you suggested is already checked. Thanks | | NickMaz Tuesday, October 06, 2009 9:26 AM | Hi,
Thanks for your feedback and the detailed description. That's really help a lot! I did a test on my machine, when a breakpoint get hit during debugging, the Start Debugging Icon is enabled (Continue F5), only the Break All button is disalbed. I suggest you go to Tools -> Import and Export Settings -> Reset all settings and see if the issue still occur.
Best regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have any feedback, please tell us.
Welcome to the All-In-One Code Framework! | | Roahn Luo Tuesday, October 06, 2009 10:10 AM | Hi, After resetting the issue still occurs. However, my mistake, when I hit a breakpoint then the Start Debugging icon IS enabled, but what I mean is that when the debugger stops without cause the icons revert to their non debugging mode. Thanks | | NickMaz Tuesday, October 06, 2009 10:52 AM | Hello Nick, Sometimes, if we step through our code, Visual Studio will take few seconds to terminate the process we attached to to stop debugging. Have you tried stopping debugging manually? For example, press Shift+F5 or click the Stop debugging button. An alternative way is to Terminate the process our debugger attached to in the Processes window. Best regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have any feedback, please tell us.
Welcome to the All-In-One Code Framework! | | Roahn Luo Wednesday, October 07, 2009 3:26 AM | Hi, I don't have a problem with stopping the debugger, it stops by itself, when I don't want it to after about 70 seconds. Thanks | | NickMaz Thursday, October 08, 2009 9:32 AM | Hi, As I understand, the issue here is Visual Studio Debugger could not revert back to the non debugging mode even after it stops, what's more, it will take about 70 seconds for Visual Studio to stop the debugger, right? One thing need to clarify here is if the debugger is not stopped, it will not switch to the non-debugging mode. I suggest you terminate the debugger manually to see if the debugger could revert back to the normal mode. I'm sorry for the inconvinience. Best regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have any feedback, please tell us.
Welcome to the All-In-One Code Framework! | | Roahn Luo Thursday, October 08, 2009 10:22 AM | Do you have any output in the output window? It sounds like the debugger is detaching for some reason. The output window should show an exit code for the process when detach occurred. | | rchiodo - MSFT Saturday, October 10, 2009 12:18 AM | There is nothing in the output window when the detach occurs | | NickMaz Monday, October 12, 2009 9:46 AM | Does the output window list anything? What does the process window say? I would guess that your development server has a timeout (probably a minute). When you sit at a breakpoint in the client for any period of time it causes the server to timeout. The server recycles itself. I'm not 100% sure how to adjust the timeout value, but this might help. http://msdn.microsoft.com/en-us/library/ms525386.aspxOr try doing a search on your app server's help. - Marked As Answer byrchiodo - MSFTModeratorMonday, October 12, 2009 4:15 PM
- Unmarked As Answer byNickMaz Thursday, October 15, 2009 9:26 AM
-
| | rchiodo - MSFT Monday, October 12, 2009 4:15 PM | The output window just lists the build data. I cannot find find a process window, is it known by a different name? It is definitely a timeout of some description but the link you sent was of no use. I have one of my projects that runs correctly and have tried importing the settings from that to one of the projects that doesn't but it didn't make a difference. Both the projects use the same web server which adds even more mystery. Also, it's not that I'm sat at a breakpoint for any length of time, I will be stepping through the code and the debugger just stops, no errors occur and it's on all areas of the code, not a particular section. It's becoming increasingly frustrating as I only get 70-90 seconds or so to debug the code before having to restart. I have searched endlessly through the help to no avail | | NickMaz Tuesday, October 13, 2009 10:24 AM |
|