With great relief I managed to work out the problem and as luck would have it I solved the problem just 10 minutes before Microsoft support called me to investigate the bug report. Thanks to Lex Li for pointing me at the support website instead of the connect site for reporting the issue.
So what was the problem? I already had VS2008 installed and had setup the symbol server settings so I could step into and see the source code for the framework Windows Forms code. This has been very handy in the past for tracking down problems by allowing me to see exactly what was happening in the base classes. Reflector is an excellent tool but there is nothing quite like stepping through the real code.
Well it seems that VS2010 was using the already defined settings and this was the cause of the issue. I removed the symbol server settings and it all working perfectly. Put them back again and it takes essentially forever to try and start-up debugging an application. It never occurred to me until I checked that VS2010 would automatically be using the same settings as defined in VS2008. I just assumed you had to set them up manually for each Visual Studio version.
April 18th, 2010 at 4:28 am
All MS products are as intelligent as their employees!
Hitesh
April 19th, 2010 at 7:44 pm
Hi Phil, glad to hear that you resolved the issue on your own :)
Yes, VS2010 imports VS2008 profile if you have VS2008 installed already. That can lead to similar issues sometimes.
Another famous issue during VS2010 RC phase is this one regarding ReSharper,
http://weblogs.asp.net/scottgu/archive/2010/02/26/no-intellisense-with-vs-2010-rc-and-how-to-fix-it.aspx
July 6th, 2010 at 4:36 am
All MS products are as intelligent as their employees!!! Very TRUE
July 6th, 2010 at 4:37 am
By the way your facebook link is not working!