Stability issues usually have nothing to do with Visual Studio. On my home/office laptop, Visual Studio is rock solid. On my work desktop, it crashes maybe once or twice a week if I do not reboot every day.
Turns out my stability issues on my work desktop was due to a bad video adapter card. Once the card was replaced, Visual Studio no longer crashed.
Many of you forget that Visual Studio is a programming environment, which is subjected to your code, the code of your macros, and the code of your add-ins. I remember the days, where depending on what you were doing, such as walking the memory chain in DOS, you would have to reboot your computer after every crash. Visual Studio is extremely stable.
From Visual Studio 2010 Readme
220.127.116.11 User code exceptions may affect designer and Visual Studio
Any user code that throws an exception
at design-time can cause unhandled
exceptions in the designer and may
even cause Visual Studio to crash. To
protect against this, prevent your
code from executing at design time by
wrapping it with
checks. Common examples of methods
that will be executed at design-time
are the UserControl.Loaded event
handler, binding converters, and WCF
async event handlers.
Just to make a point.
From Another Prespective
Notice all crashes disappeared after switching out video card. See < http://superuser.com/questions/152524/wpf-visual-studio-2010-premium-frequent-crashes>.
Just to make the point again.