Hans, Check out this post I found:
http://social.msdn.microsoft.com/Forums/en/vssetup/thread/69925677-8a07-46a4-8b0e-c9ddef17a7af Give the workaround a shot - it looks like it could be a problem with VS2010 not finding the .net assemblies. The working one has VS2008 installed, which leads me to think that the VS2008 install either put the assemblies in the same location that VS2010 is looking for them, or it set some registry key that points to the right location of the assemblies (that is, of course, if the workaround... works :) ). Josh On Jan 17, 4:41 am, Hans <[email protected]> wrote: > On 14 ene, 11:16, Josh <[email protected]> wrote: > > > Hans, > > > I've seen a bunch of MS bug reports about the same issue. > > > Have you installed the beta for Visual Studio 2010 SP1? Seems to be > > related. > > > Josh > > No, I haven't installed it. I've read most people having the issue > have it installed. > It seems to be related to Visual Studio 2008 as I have 3 computers; 2 > of them having the issue (fresh installed Win XP and VS 2010) and the > one working has VS 2008 installed. > Any thougts ? > > hans
