As of this date, Oct 19, 2011, I too had the same problem.
Apparently ... as far as I can tell ... a new install of .NET (version 4) being performed for an unrelated project created a problem with...