VS 2010 Ultimate: Binding ProteusDebugEngine Debugger to Error Process

Question

When I load a C # /. NET 4 project into VS 2010 Ultimate on my main machine (Win 7 Ultimate 64 bit), I get an error

Attaching the ProteusDebugEngine debugger to process '[XXXX] YYYY.vshost.exe' on machine ZZZZ failed. The debugger is not properly installed. Cannot debug the requested type of code. Run setup to install or repair the debugger. 

This happens when I set the target to “Any processor” or “x64”; I do not receive this message for x86 target.

I already uninstalled and reinstalled VS 2010 twice, and also tried the repair. Manually re-registering oleaut32.dll also does not help.

When installing VS 2010 Ultimate on my laptop (Win 7 home premium 64 bit), I do not receive this error message at all.

Both machines have pretty similar software setups. VS 2010 Express is also installed on both machines, and I do not get this error with it on either of the two computers.

Help on this would be greatly appreciated.

Answer 1

I recently ran into this problem, but besides that, I also came across another error message that appeared in SQL Server Management Studio when I tried to connect to a server that says:

Cannot pass COM object of type "System .__ ComObject" to interface type "Microsoft.VisualStudio.OLE.Interop.IServiceProvider" ...

so this time I googled for this error and found a solution that I found in the links below:

Martin Poon - Microsoft MVP Blog - Unable to use COM type type ...

Stack overflow - unable to pass COM object of type "System .__ ComObject" to ...

Thus, it seems that these problems occur when you install a new version of Internet Explorer on your windows manually or through a Windows update. in my case, this is due to installing IE9 using a Windows update on my Windows 7 x64, which was fixed by following the instructions with the above URLs.

or briefly:

 open Command Prompt as Administrator and execute below command(s): regsvr32 "C:\Program Files\Internet Explorer\ieproxy.dll" for 64 bit windows, also try this: regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll" 

and voila, both problems just disappeared :-)

Answer 2

The same message appeared after installing Visual Studio Ultimate 2010 on the new system. I pulled the source from tfs and collected everything. The configuration was configured for any processor for each project, however, the setting at the top was "mixed", as soon as I set the general type in AnyCPU and cleared the solution, it started working fine in the debugger.

Answer 3

Doing the following at the command line of Visual Studio (2010) resolved this for me.

 devenv /resetskippkgs 

Answer 4

In my case, it helped:
1. Open project settings
2. Uncheck the “Prefer 32 bit” checkbox in the “Platform Objectives” section of the “assembly” tab.