If you are like me and you store all your code on a server, you will have likely learned about trusting a network share using CasPol.exe. However, when moving from Visual Studio 2008 (.NET Framework 2.0/3.0/3.5) over to Visual Studio 2010 (.NET Framework 4.0), you may find yourself scratching your head.
My movie induced optimism for Office 2010 was quickly shattered this week after trying out the beta on my box. Having followed the best practice of uninstalling Office 2007 and rebooting before installing the beta, I was not prepared for the days of frustration that would ensue. After several hang dumps and a few days of futzing around, it was discovered that installing Office 2010 corrupts the Visual Studio Web Authoring Component. A quick search of Google also confirmed that this was a recurring issue with others as well. Martin Hinshelwood suggests repairing the installation. However with the prolific use of Visual Studio 2008 internally, I fail to understand how such glaring fault was allowed to slip through for a public beta. My suggestion is to uninstall Office 2010, go back to Office 2007 and wait for the next beta. This is a milestone that is obviously too early to be public.