Visual Studio 2008 closes unexpectedly_问答_开发者

Visual Studio 2008 closes unexpectedly

开发者 https://www.devze.com 2023-01-04 01:03 出处：网络

I don\'t know if I can really get an answer to this question, but it really irks me and I would like to know if someone has an idea how to arrive to an answer.

I don't know if I can really get an answer to this question, but it really irks me and I would like to know if someone has an idea how to arrive to an answer.

I have a pretty large solution in VS 2008 that maybe every week/every other week whenever I click properties to get to the project properties the IDE closes without warning. After that happens it will close EVERY time I try and view the properties. At that point I try and delete the .suo file, I resize the IDE, I close the tabs within the project, I restore default VS Settings(when I'm desperate). Eventually 20-30 minutes later I can actually view the properties. I haven't figured out exactly what fixes it, seems to be different every time. Once it's "fixed" I can't break it again so I can figure out what "fixed" it.

This seems to be project specific, because I can view properties of other projects while this project is misbehaving.

I guess my first question is, does VS log reasons for closing unexpectedly? Can I find out what the offending reason behind this is? The main frustration is I don't know the cause, nor the cure.

Any ideas?

UPDATE:

The solution is a WPF Application with 3 library projects added in.

I have the following add-ins:

Test Driven.NET 2.22.2468
Xaml PowerToys

I can disable these, and then see if it still does it. But like before, it is not easily tested because it seems to randomly not work.

I use the properties tab quite a lot because we are using Click Once depl开发者_JAVA技巧oyment and I go to the properties tab to publish the latest build.

Another possibility is that I have dual screens and I downloaded a utility called MultiMon which lets you manage both screens better. Maybe that's jacking with VS and window messages are getting confused and killing the app process.

Take a look how much memory VS is using, and how much you have available. If you are reaching close to 1.5GB memory usage, VS is under heavy pressure, and if you don't have at least 4GB on your box that would be the case as well.