I cannot start the debugger in VS 2010 under Windows 10. I've been using VS2010 for many years now but just recently moved to a new dev box under Windows 10. This just started a few days ago. Prior to that I as able to launch the debugger without issue.
I can start without debugging Ctrl+F5 but F5 or clicking the green start arrow will not work. I can see the development web server open and there's a flash of the screen but IE never opens and the app returns to the "stopped" state within a few seconds.
I've been looking through all of the suggested options but nothing I have tried has worked so far. The other day I got it working by doing a clean and then rebuild all, but that hasn't worked today.
Related
I am battling with this issue since months, begin just after I installed VS 2022...
If I start my web app (either with debug or without debug) from VS, the browser windows launches, and after that I am unable to switch desktop windows by clicking the icon on the Windows taskbar. This applies to all running application icons on the taskbar
It seems, that VS brings the browser window to the top, with some way what fools Windows.
Diagnostics:
it is not just VS and the launched browser, say I had open a console window, after the web app launch I am unable to switch to the console window by clicking its icons on the Windows taskbar.
after I switch to other windows with other method, say alt + tab, the window handling still remains fooled, it does not work.
Configuring VS to use Edge or Chrome does not matter, both case produces the issue
Exiting VS, closing the browser window resolves the weird behavior, of course next time I launch a web app with VS the issue is back.
Using Windows 11, but no other app exhibited the issue, it is just VS when launching the browser.
Question
This is a real productivity killer for me, breaks my work hundred times a day. Does anyone experience this issue, if yes, has anyone workaround for it?
Currently I found only this workaround:
Options/Debugging/General: turn off 'Enable Diagnostic Tools while debugging'
I have an intermittent issue when trying to debug local IIS sites.
Visual will hang and eventually displays the error:
The web server did not respond in a timely manner. This may be because another debugger is already attached to the web server
If I wait a minute and hit "Start Debugging" again it will work (sometimes I may get the error several times but it eventually works).
There is nothing in the Event Viewer around the times I try to debug.
The app pool is .net V4.0 Integrated.
I am running Windows 8 Pro with IIS 8 and Visual Studio 2010.
Also its a site using EpiServer 6 R2.
I have tried IISReset, stopping/starting the site, closing and reopening Visual, rebooting my machine. None of that seems to make a difference, its hit and miss whether the solution will debug or not.
Once the solution is debugging, it runs fine without issue. Until I stop debugging and try and start debugging again.
The site runs fine in all other aspects, its only when I try to debug.
So... I never fixed this issue, but have since upgraded to a solid state drive. So I now have a fresh install of Windows 8 Pro and Visual and the issue has not resurfaced.
I have an ASP.NET web application that I've been working on for the past few months. Recently I've encountered a problem where when I start debugging and internet explorer launches it locks up. I've tried waiting, but it hangs indefinitely. This happens about 75% of the time. I know it will lock up if the progress bar doesn't show up in the footer. If the progress bar appears then everything works fine. It's turned into a ritual of starting/stopping debugging until it works. If I use Firefox everything works fine. However I can't avoid IE forever as this application is being used in a closed environment where all users are using IE8 exclusively.
I know it's not code related as everything was fine on a Friday, and then with no changes made, it started behaving this way on Monday. I've also opened other web applications and they suffer from the same problem.
I've made sure everything is up to date in Windows Update. I've looked for any updates/fixes to Visual Studio 2010. I haven't been able to find any posts anywhere describing this problem. There's nothing in my logs showing up either.
I'm running Windows 7 SP1 64-bit with VS2010 SP1.
Edit: I've also tried running the solution with IIS instead of the built in dev server, but it had no effect.
When I stop and re-run the debugger in Visual Studio against a Windows Mobile 6 device, the emulator restarts each time making the debugging experience extremely slow. I could understand if I made changes to the code, but this is happening regardless of whether changes are made.
Is there any reason why Visual Studio would restart a new emulator each time? How can I ensure that the debugger uses the same instance of the emulator that is already running?
I figured it out. I had multiple projects within the solution for various assemblies and the emulator type set for each project was sometimes different and thus causing multiple emulators to fire up. When I closed the multiple emulators Visual Studio would then re-start them all next time I went to debug.
I have VS2010 Professional edition and I recently started getting problems debugging an MVC website. The debugging at the Controller code is very slow and each F10 command takes 20 seconds to move to the next line.
Javascript code debugging is quick. I tried a console app and a Forms app and debugging is quick. I also tried creating a blank new MVC app website and the debugger slows down. I am using IIS7.0. This recently started happening as I recently installed VS2012 Ultimate RC. I thought it may be the reason and uninstalled all the software VS2012RC Ultimate installed on that day and the debugger retuned to normal. Looking at task manager devenv.exe was using about 1GB of memory and w3wp.exe was also consuming memory and increasing to 800MB. Has anyone recently installed VS2012 RC Ultimate alongside VS2012 Professional and got into similar problems? Does any one who what is the rootcause of this problem?
Try setting IntelliTrace to collect events only in Options -> IntelliTrace -> General. This might speed up debugging.