Home Dashboard Directory Help
Search

Crash when loading the toolbox by Larry Middleman


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


1
0
Sign in
to vote
Type: Bug
ID: 686628
Opened: 9/1/2011 4:53:06 PM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

I have a fresh install of VS 2010 Express Web Edition (I also have the C# edition). The Extension manager only shows the Nuget Package Manager is installed. Whenever I mouseover the collapsed toolbox, or load a designer that loads the toolbox, the IDE crashes.
Details
Sign in to post a comment.
Posted by Microsoft on 9/8/2011 at 4:48 AM
Hi Larry Middleman,

Thanks again for your feedback. We are glad to hear that the problem had stopped troubling you. We'll go ahead and close this Connect issue.
Thank you for using Visual studio Connect site.
Posted by Larry Middleman on 9/3/2011 at 6:51 AM
I noticed that some silverlight content on the net was not working even though I had Silverlight 3 & Silverlight 4 developer runtime installed. So I uninstalled all Visual Studio 2010 editions, all silverlight components. Deleted the %ProgramFiles%\Microsoft Silverlight folder. I deleted the registry key HKEY_CLASSES_ROOT\Installer\Products\D7314F9862C648A4DB8BE2A5B47BE100 because the Silverlight uninstaller was generating an error. Then I deleted the registry keys HKLM\Software\Microsoft\Silverlight, and HKLM\Software\Microsoft\SilverlightTools.

Then I reinstalled latest VS 2010 Web Edition and the Silverlight 4 tools for VS 2010. Then I ran Windows update which applied about 8 patches to VS, .Net 4, or Silverlight.

Now the problem appears to be resolved.
Posted by Larry Middleman on 9/2/2011 at 8:04 AM
VS Express debugger does not allow attaching to a process. I used procdump to get a dump and uploaded that. The page you linked does not talk about how to get a callstack.
Posted by MS-Moderator09 [Feedback Moderator] on 9/1/2011 at 11:25 PM
Thanks for reporting the issue.
In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

It may help if you provide us with a mini dump file and call stack. If you have Visual Studio 2010 installed, you can use the following steps to get a mini dump file:
1. Start Microsoft Visual Web Developer 2010 Express.
2. Start an instance of Visual Studio 2010.
3. In the instance of VS click Tools | Attach to Process...
4. In the list of processes locate VWDExpress.exe.
5. Click Select... and explicitly choose 'Native' and 'Managed' code.
6. Click OK and OK to close Select dialog and Attach to Process dialog.
7. Go back to Visual Web Developer Express and repro the crash.
8. Upon the crash, control should go to the instance of VS.
9. In the Visual Studio 2010 click Debug | Save Mini Dump.

If you are running the VB profile you will not see the Save Dump As menu item. To add this menu item:
a. Select Tools -> Customize
b. Select the Commands tab
c. Select Debug from the Menu bar dropdown
d. Click Add Command...
e. Select Debug from the Categories list.
f. Find the Save Dump As entry in the Commands window.
g. Click OK (the Save Dump As... command is added to the top of the Debug menu).
h. Click Close

If you do not have Visual Studio 2010 installed, I recommend to use procdump to get a dump file.
You can get some more details of procdump from: http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

You can get detailed steps about how to get the dump file and call stack at http://blogs.msdn.com/debugger/archive/2009/12/30/what-is-a-dump-and-how-do-i-create-one.aspx


Please package your files into a zip file and name the zipped file Feedback-686628.zip.
You can upload the file to workspace:

https://sftasia.one.microsoft.com/choosetransfer.aspx?key=5d606cdd-4289-47af-bd1d-6ab77876dfe7
Password: @tlZ3+cda

It would be greatly appreciated if you could provide us with that information as quickly as possible.

Thanks again for your efforts and we look forward to hearing from you.
Posted by MS-Moderator01 on 9/1/2011 at 5:40 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.