I would like to add my support for the observations above. We migrated to VS2010 but within a week were forced to revert to using VS2008 due to the number and severity of bugs and performance issues.

The worst problem is that we have to recompile the entire application whenever we make a change to one of the resource header files. This is an absolute productivity killer. We submitted this as a bug ( https://connect.microsoft.com/Visual...t-source-files ) and were told that, despite the severity of the issue, it would never be fixed in VS2010. This is ridiculous. We were going to stick with 2010 in the hope of the problem being fixed in a patch but being told that the issue wasn't sufficiently serious was a major blow. I can't imagine what other problems there must be if this issue is regarded as being too trivial.

There are, of course, all sorts of other performance issues with Intellisense etc. that we hoped to see fixed but our confidence in Visual Studio is at rock bottom and sinking...

God knows, VS2008 has enough performance issues of its own but it is still far better than 2010. I'm sure all the shiny new stuff is great but it's no use if the editor is unusable. Why not try getting the basics right (like making the resource ID editor dialog resizable so you can actually see the IDs - very, very simple).

It's a shame that all the great new stuff is ruined by the lack of attention to detail and the arrogant no-can-do attitude. I suspect if there was a suitable alternative development environment then you would be motivated to fix these issues. Then again, if there was an alternative I'm sure we wouldn't be using Visual Studio at all.