Visual Studio 2008 SP1 crashed on Vista x64

17 February 2009

For the folks looking for an answer:

I had something happen today that normally doesn't happen.  I loaded a solution, and Visual Studio just closed.  No error message, no dump.  It just stopped.  Gone.  I tried many, many times, and it crashes silently when opening one particular solution.  It works fine on every other solution.  At first, I thought I'd disable my add-ins, so I disabled:

  • ReSharper
  • Gallio
  • TestDriven.Net

I even reinstalled PowerCommands because I found someone who had a problem with that.  Nothing worked.  I finally started thinking about the variables.

The one variable I missed was that this solution had last been worked with before I upgraded to Visual Studio 2008 SP1.

Solution:  I deleted the *.suo and *.cache files next to my solution file.  I reopened the solution, and everything is fine.

Read More     10 Comments


Trackbacks

KB963676 fixes Visual Studio 2008 SP1 crash on Vista x64 Posted on 3.03.2009 at 1:02 AM

I blogged earlier about VS 2008 SP1 crashing silently when pulling up a web form or master page designer. KB963676 is what I have been waiting for. It was made public just last Thursday on 2/26/2009, and the hotfix fixes the crash for me. The KB description

Comments

Andrei Rinea said on 2.17.2009 at 7:17 PM

Shameful of the Visual Studio team to have their product crash **WITHOUT** a log, a trace...something.

I am having difficulties with VS2008SP1 on Vista 64 too, but my problem is that the worker process of a/the web application goes into an infinite loop on a non-user thread very often. It makes no difference if it runs under Cassini or IIS7. It does the same thing :(

Any idea?

Padgett Rowell said on 2.17.2009 at 9:30 PM

Is this an MVC app? If so I've been suffering from the same issue. VS seems to crash whenever you open a view. My workaround is to:

* open a blank MVC app first

* open any view

* from the start page, open my current solution

Ryan R. said on 2.18.2009 at 12:11 AM

I had the same issue with an MVC app (in fact it was any .aspx file, not just views). For me it was Gallio, because it worked fine when I uninstalled the app but I didn't get a chance to pinpoint which part of Gallio was causing problems..

Gilligan said on 2.18.2009 at 7:45 AM

I had a similar issue with ASP.Net MVC. I am using a Website Project and installed RC 1 with the Web Platform Installer. But I also was bin-deploying the MVC binaries. I ended up having to uninstall the the RC 1 and just pasted the binaries manually.

Johan Idstam said on 2.18.2009 at 8:34 AM

When that happens to me I go to Tools/Options and turn off Source Control before I load the solution.

Steve Sheldon said on 2.18.2009 at 10:27 AM

I've been seeing the same thing with ASP.NET MVC projects. Although usually for me I just reopen the solution and it usually works.

Jeffrey Palermo said on 2.18.2009 at 12:30 PM

I haven't seen the correlation with the project type (in my case). The .suo or .cache file was the culprit.

Bill Pierce said on 2.18.2009 at 4:23 PM

I am experiencing the same issue. Deleting .suo and .cache files did not solve it, but Padgett's workaround addresses my issue.

Ben said on 2.23.2009 at 10:51 AM

I noticed in ASP .NET RC1 install/upgrade release notes, that PowerCommands is listed as having problems with it.