VS 2010 very slow

Question

I have just upgraded to VS 2010, and I have performance problems which I did not have before (in VS 2008).

The most annoying thing is that it freezes while I work in the text editor. Sometimes when it freezes I see that it is saving auto recovery information, but not always.

Almost anything I do gives an unacceptable long delay, like saving, starting to debug, ending debug session, switching between design and code view, and doing WinForms designing.

I have some parts of my home directory on a mapped network drive. I suspect that that might be a part of the problem. Is it possible to configure VS 2010 to use exclusively local disk for its "internal" work perhaps?

Any hints would be appreciated! Has anyone else experienced these kinds of problems?

Edit: I forgot to give my specs:

• Win 7 64-bit
• 4 gb memory
• No addins, just standard installation
• The project folder is on the network drive

One interesting thing is that I feel that I have better performance in a VM running XP (where the VM runs on the same PC).

Answer 1

VS is great if you do what microsoft recommends and work on a local copy of your projects. As soon as you start tying to open projects in remote locations you will get this issue.

Recommendations:

1. use a source control solution.
2. create a copy of your project locally and run the solution from that.

Also ...

I think it does it's clever stuff in the background, I found the more i use it the faster it gets, especially on long running projects that I regularly go back to.

If you think it might be aformentioned WPF framework you may want to try switching off aero (as a test) if it helps the problem is likely that your chosen graphics hardware is not very good at effect or 3D based output so it's struggling.

Also try reducing the number of background services and apps you have running.

on windows 7 these days 4 gigs of ram is considered standard, so whilst it should perform fine maybe consider putting more ram in if you are trying to handle large datasets / similar business applications.

Another thing you could try is run a repair install over the top of your existing, it may not have cleanly installed something ... unlikely but it may help.