I'm going through the problem of setting up a new computer and I'm having a problem with VS 2005. Whenever I start debugging all the windows (properties, watch, errorlist, stack, ...) pop up all over the place undocked. At this point I've tried docking them and closing them. When I stop debugging more windows pop up all undocked. This keeps happening over and over and over... I've tried closing and docking them but they keep popping out. Wasn't sure how to google this and my patience has grown thin with this whole process of moving to a new comp.
Sincerely,
Frustrated
This thread about resetting your settings might be helpful (even though it says VS2008, it still applies to 2005).
Related
Since some days Visual Studio is stealing the focus. The weird thing is, this happens when using other applications in Windows (such as Chrome) but also when working in Visual Studio (such as typing).
My considerations so far:
It only happens when VS is running.
Happens in VS 2012 Premium and in VS 2012 Professional.
Also happens in Safe Mode.
Tried reinstalling. No success.
Uninstalled 3rd-party extensions. No success.
The focus goes to "nowhere" - I don't see any application or window having the focus. Also a [Windows]+[Array up] does not maximize anything.
[Alt]+[Space] has no effect.
[Alt]+[F4] has no effect.
I'm running Windows 8.1.
Does anyone have an idea what the cause is, or what I can do to further analyze it?
It seems I found the cause by disabling background tasks step-by-step. The focus stealing was gone when I killed the QuickSet application on my Dell XPS 13. I also read on Dell forums that others were having similar problems with focus stealing. The strange thing is, that it only happened when VS was running.
But anyway, as VS is more important to me I decided to split up with QuickSet. :'-(
After my laptop fell on the floor and its screen was a little damaged, I was able to continue working with it, but failed to build a project of mine. At some point, the system froze, and I was forced to restart the laptop. Ever since, I’m not able to start Visual Studio 2008 or 2010. Moreover, when I do try to start one of the versions, I see no splash screen, and at some point, all running applications stop responding, and I’m forced to restart the laptop.
When I started Visual Studio 2008 with the /SafeMode flag it started OK and worked perfectly, but when I tried it with Visual Studio 2010, I did see a splash screen and the application main window was opened, but then the system got stuck again and forced me to restart.
I use Windows XP SP3, and the addins I recall I have are Visual Assist, IncrediBuild, and Productivity Power Tools for VS 2010 (how can I check what other addins are installed without having Visual Studio running?)
I tried using the /Log flag to find out what’s happening, but there was nothing that seemed related in the generated log.
At the time of the hang, the CPU and memory of the system was low.
The problem happens whether I open Visual Studio with no solution, or with an existing solution.
Do you have any idea why this might happen, or how it can be solved?
Edit:
I run chkdsk /R /V and it is stuck on "1 percent
completed." for hours now. Is there anything I can do?
I'll try to re-install Visual Studio 2010 next week, when I'm in the office. I hope that will help.
Thanks a lot,
splintor
Your drive is torched. Buy a new drive, and salvage whatever you can from the existing drive, then swap them out. If you're lucky you can salvage enough of the existing drive to not need to do a full OS reinstall, but it's likely you're going to need to do some reinstallation.
Looks like the cause if the fall of your laptop. Though what changes happened is unknown it is more likely to be a hardware issue.
Did you reinstall the softwares and check how they work.
If I was diagnosing this issue, I would start from the ground up.
Start of with a basic CheckDisc - CheckDisk Instructions for XP
Progress from that to try re-installing over your existing VS install.
I can't see it being a software problem, so I reckon the checkdisk will discover/fix something, or a reinstall should resolve it.
Dave
You've probably damaged your hard disk in an area which is touched by VS. Windows often grinds completely to a halt when it's struggling to read a damaged area of disk.
Check the Windows event log for errors to do with disk drives.
EDIT #3 : Microsoft has released a 'fix' to this problem which is available here. I haven't had the time to test it, but I those who want to are welcome to leave their feedback here !
Sometimes when I run an application from Visual Studio and it crashes or I stop it using the stop button in the debug menu (Debug->Stop Debugging (Shift-F5)), the console of said application stays open... and never closes. I cannot close it by clicking the 'x' button in the top right corner. I cannot kill the process as it is not even listed in taskmgr.
I have seen this problem documented in different places on the web, but no solution so far.
I am running on windows XP SP3, using visual studio 2008 w/ SP1.
1- What could be causing this ?
2- Is there a fix ?
thanks alot.
JC
EDIT: There is no MyApp.vshost.exe process to close, and closing visual studio does not close the console either. Worse even, if I try to restart my computer windows will hang and never close, I need to do a forced shut down.
EDIT #2 : (from Brad Sullivan, Program Manager - Visual Studio Debugger on March 2nd)
[...] this issue is likely not in Visual Studio since it also occurs in scenarios where Visual Studio is not present. We are in the process of handing over our investigation to the Windows Servicing team.
But for now, removing the KB978037 update and it's related files seems to work.
This is a bug introduced in security update KB978037. Back out this update and you'll be back to normal.
Also see here:
http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/e6d4a4f5-7002-401a-90e1-6174d7f9e3ca
Microsoft has released a 'fix' to this problem which is available here. I haven't had the time to test it, but I those who want to are welcome to leave their feedback here !
There are a couple of things that could be happening here. Try closing down the following process and see which one, if any close down the Console application as well.
The Hosting Process: Typically named YourExecutable.vshost.exe
Visual Studio
If closing the hosting process fixes the issue then one quick work around is to disable the hosting process itself.
Right Click on Project -> Properties -> Debug -> Uncheck the hosting process
If closing down Visual Studio fixes the problem then it's potentially a bug in Visual Studio. Please file a bug on connect.
http://connect.microsoft.com
Visual Studio Debugger Team has already acknowledge this issues on their blog. check the below url for more information.
http://blogs.msdn.com/debugger/archive/2010/03/11/help-my-console-windows-won-t-go-away.aspx
Any time i try to debug in visual studio 2008 my entire system will freeze whenever a breakpoint is hit.
I can move the mouse around and that remains responsive but nothing i click on does anything,
I can bring up the task manager but can't do anything with it and i am able to lock/unlock the machine.
I tried a fix that i found via google that suggested i disable advanced text services but it didn't work. I am using visual studio 2008 with SP1 running on Windows XP Pro, asking here is my last hope before formating/reinstalling so i hope someone can help me out.
I debug by running the application in debug mode, the freeze happens no matter what the project size and it seems as if it is just the entire GUI that freezes, the computer carries on working just fine i just can't do anything with it because the GUI is totaly unresponsive.
I found I only had this issue when I was using the keyboard to debug. If I used the toolbar debug buttons, I didn't have an issue.
To "fix" this, I set the LowLevelHooksTimeout to 300ms (from 5000ms). You may need to add the DWORD if it isn't already there.
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows\Control Panel\Desktop\LowLevelHooksTimeout
HKEY_CURRENT_USER\Control Panel\Desktop\LowLevelHooksTimeout
Restart after making this change for good measure.
How big is the project you are running? When I did a Find last night on a huge open source project, I got kind of the same behavior.
Also, did you try Uninstalling just VS2008, then Reinstalling with only the options you use.
Have you tried disabling "Call ToString()" debugger option? This is ON by default, and is known to deadlock.
When I press F5, everything compiles fine, but when the app is to be started, VS crashes, showing the "Just in time debugger" dialog.
More than one (similar) solution has this problem. A new solution containing just a form, works. This problem started out of the blue, I have made no changes to the environment as far as I can understand.
I can start the app without debugging (ctrl+F5), and then attach the debugger.
I'm using VS 2008 sp 1.
Never seen this issue, have you tried turning off all your plug-ins like reSharper, CodeRush, etc.?
Update: When worst comes to worst I usually try this command line.
devenv.exe /ResetSettings
devenv.exe /ResetSkipPkgs
devenv.exe /Setup
try all these you can do them all at once or do them individually it is up to you. But be aware that you will be deleting all your settings that you have customized in to Visual Studio, so you may want to back them up.
The last thing you can try is this, to see if the problem is with something weird that is running.
devenv.exe /SafeMode
Starts Visual Studio in safe mode, and loads only the default environment and services, and shipped versions of third-party packages.
I've found the problem now. I had "Step framework source" enabled, which somehow broke the debugger (strange though, because it usually works). Turning that off, made me debug as usual again.
If you have undocked windows in debug layout search KB960075 on code.msdn.microsoft.com (can't add hrefs).
Do you have CLI.exe error issues? Check your event log. I've had the same issue and simply re-staged my machine out of panic since I was so near a deadline. I assumed that it was an issue with the registry and couldn't find an answer.
try repair or reinstall, don't waste time findin' the reason of the problem
I had the same problem, out of the blue the IDE would crash when I started to debug. Happened with any existing project that I opened, even the visual studio samples. I created a new project, just a blank dialog, ran it, and all was good. After that, the problem went away and I was able to debug again.
This happened to me just now, after my computer rebooted itself last night. When I was pressing F5 the app started but instantly shut down and the VS IDE crashed.
To fix it: Debug->Delete All Breakpoints. It worked for me.