I am using VS.Net2005. Whenever I open a project, the VS gets stuck. If I end the vshost process, the VS continues to respond (but I cannot debug the app). The same happens when I create a new project, so it is not a project specific issue.
Does anyone know how to solve the problem
thanks.

vs 2005 not responding
Dave Yuhas
Thanks for the call stack. Apparently the hosting process is failing very early, leaving Visual Studio in a deadlock condition. What we need now is a call stack of the hosting process itself.
[1] Install Debugging Tools for Windows. You can install them from http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx (assuming you're running on a 64-bit machine; other platforms are also supported).
[2] Run the scenario up to the hang
[3] Change to the directory where you installed Debugging Tools for Windows
[4] Run windbg (with no command-line parameters)
[5] Attach to vshost.exe
[6 ] Hit Ctrl-Break. Type in the following command in WinDbg (at the bottom of the screen, there should be a single-line textbox for you to type commands in):
.dump /u /o c:\dump.dmp
Also, to get you unblocked - you can disable the hosting process. Unfortunately, as another message states, Visual Studio is frozen as soon as you open the project (or create a new project). You can terminate the vshost process. This will allow Visual Studio to return. Change the project property to disable the hosting process. Close and reopen the project.
Alternately, you can update the csproj file directly by editing it in notepad. Add "<UseVSHostingProcess>false</UseVSHostingProcess>" to the 'Debug|AnyCPU' PropertyGroup.
Ben Isbell
Hi Liat, firstly, you should still be able to debug your project even without the hosting process enabled. The hosting process provides a faster experience but is not necessary for debugging unless you're using security features such as 'Debug in Zone'. So when you say you can no longer debug, what exactly is it that you're seeing And what are the steps that you are taking to disable the hosting process
Secondly, are your projects located on a network share (you can check this in the Tools->options->Projects and solutions field). I'm wondering if you're experiences some network related lag when opening projects.
-Prasadi
redfox70
Thanks Alexey, I received the .zip file. I'll get back to you as soon as we have had a chance to look at the dump data.
-Prasadi
nutsboutdan
Can you turn off the VS hosting process before you start debugging (i.e. before it hangs)
-Prasadi
kurbylogic
Oh I see. Do you have any Anti Virus software installed We've seen one other issue like this before that was caused by an anti virus program. You can find more information about that here: http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx FeedbackID=108974
That particular problem was resolved by removing the virus SW, repairing the VS install and re-installing the virus software.
If that's not your scenario, can you please follow the instructions below to get some further information to debug the problem Let me know if you manage to get a mini dump in this way.
[1] Install Debugging Tools for Windows. You can install them from http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx (assuming you're running on a 64-bit machine; other platforms are also supported).
[2] Open a command prompt
[3] Change to the directory where you installed Debugging Tools for Windows
[4] Type in the following command:
windbg -G -g <full_path_to_devenv.exe (in quotes if necessary -- omit the angle brackets>
This will run Visual Studio under WinDbg, which is a low-level debugger that can be easily used to gather a minidump. We will want to obtain a minidump at the point of the hang.
[5] When VS starts, run through the scenario that makes the problem happen.
[6 ] At the point that you see the hang, switch to WinDbg. Hit Ctrl-Break. Type in the following command in WinDbg (at the bottom of the screen, there should be a single-line textbox for you to type commands in):
.dump /u /o c:\dump.dmp
Clemens Vasters
and I cant figure which tag and value in .proj (I tried to do this manually) file corresponds to this option, I should uncheck.
MichealCollins
Hi Liat,
Can you take a look at this forum question and the answer at the end to see of it helps you
http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=250018&SiteID=1
Also, the following link has some useful info too
http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=135520&SiteID=1
Do let me know if any of this solves the problem.
Thanks
Suma Sushilendra
Martin Tirion - MS
And after resetting all settings to default VC# developer i received a new error msg - "Attaching to managed debugging process [ProcessID] on <MyPCNAME> failed"
I understand that here something wrong with debugger. But I not sure how to fix this issue.
All OK on VS 2003 installed on the same machine.
Is this can be affected by any domain security policies
Is there any article with detailed debug requirements (permissions on files\ security priviledges etc...) for VS 2005
kefei
Hi,
Can you give more information on the issue you are seeing
Like,
-What language projects are you trying to open or create
- What VS SKU (like express or Visual Studio Team System, Pro etc) and what OS are you using
- What do you mean by VS getting stuck Does it become unresponsive or hangs If yes, can you try killing the devenv.exe process and send the watson error report and get the watson bucket ID from event viewer and post it in the forum
Here's how you can get the Watson bucket id from event viewer on Windows XP.
1) Click Start, and then click Control Panel. Click Performance and Maintenance, then click Administrative Tools, and then double-click Computer Management. Or, open the MMC containing the Event Viewer snap-in.
2) In the console tree, click Event Viewer.
3) Select "Application Log" and look for an "error" type of event from "vcsexpress" or "Devenv" source and a subsequent "Information" type of event from the same source. Select the "information" type event, right click, go to properties and post back the big number you see in the "Description" pane.
Thanks for reporting this issue, please post back with the answers and I hope I can get some help for you.
thanks
Suma Sushilendra
Ariane Jansen
The projects are regular English projects.
I am using VS 2005 Pro. OS: win2k pro.
The VS stops responding. In task manager it also says that the app is not responding.
When I create a new project (simple console application), I see that the files are opened, I can see the generated main method, and it says that the project creation was successfful. Then the VS stops responding. It stops painting itself. If I kill the vshost, the VS becomes responsive again, but I can no longer debug any application.
No DrWarson dump was created.
The only error in the event viewer is the following:
.NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error (7A2B45A2) (0)
thanks,
Liat
Eddy Fuchs
Alexey, could you try turning off the Visual Studio hosting process to see if that makes a difference to your scenario (Project Properties->Debug (uncheck 'enable the Visual Studio hosting process).
That could help us to narrow down the problem somewhat.
Thanks,
-Prasadi
mannato
Anyway, according to debug data there is not an AV, that caused troubles.
This is latest dump data from windbg window:
ModLoad: 54a60000 54ada000 C:\Program Files\Microsoft Visual Studio 8\Common7\Packages\Debugger\cpde.dll
ModLoad: 5e380000 5e409000 c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\diasymreader.dll
ModLoad: 63e90000 63ed9000 c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscordbi.dll
ModLoad: 63d70000 63e36000 c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscordacwks.dll
ModLoad: 54a30000 54a51000 C:\Program Files\Common Files\Microsoft Shared\VS7Debug\csm.dll
complete zipped file I just send to your e-mail. I hope it helps
Alex Ellis
I am afraid that the problem is not solved.
I uninstall all add-ons (and any unused application), and tried to re-install VS. Still I get the same problem.
Also, the problem happens even when I create a new console application, which has nothing special in it.
I simply can't open ANY project...
I read that it might have something to do with WWF. However, I never installed it, and I don't see it mentioned in the Add\Remove programs.
I had VS 2005 installed on this machine, and worked with it. After a couple of months without using it, now I have those problems...
Any suggestions I am afraid that the next step would be formatting the PC (which is something that I would really like to avoid).
thanks!
Polizei