I had the same problem, solved it by disabling the "Visual Studio hosting process" ("Project" -> "[ProjectName] Properties..". -> "Debug" -> Disable "Enable the Visual Studio hosting process")
Whats the purpose of this "Visual Studio hosting process"
Maybe I found the problem.... The solution configuration is on "Release". the problem is that i cannot change it to debug, cause the combobox in the toolbar is gray. and even from the project properties from the menu i am unable to change to Debug.
I don't know if it is an express problem or express restriction.
i don't know if it can help but there's a service called .NET Optimization Runtime Service.... i don't know what it stands for, but maybe it will help :)
Thanks for your efforts ZAiNT. Both your work around, and the work around of disabling the Visual Studio hosting process actually have a fairly similar effect on how the debugger works internally.
Since it sounds like several people have run into this, if possible we would like to know what the real problem is. So if you have the time, could you let us know:
If you start a managed process outside the debugger (Ctrl-F5), are you able to attach to it (Debug->Attach To Process)
If not: At which point does it fail If you have a SKU that also supports native debugging, are you able to debug the native code in the process
This is sounding like some sort of DCOM/RPC configuration issue, but it is hard to know for sure. Luca, you said that you tried with attach, do you mean you tried with 'Tools->Attach To Process' Which part fails -- listing processes or attaching
It sounds like everything is experiencing this problem for managed projects. Do you still have this problem for native projects How about attaching to a native project (example: notepad.exe)
If you start a managed process outside the debugger (Ctrl-F5), are you able to attach to it (Debug->Attach To Process)
No, I start the process (Ctrl-F5) and as soon as I click, Debug->Attach To Process, i get the 'Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named 'COMPUTERNAME'. The binding handle is invalid.' messagebox.
'If you have a SKU that also supports native debugging, are you able to debug the native code in the process '
I'm not really sure what you mean by this so I think you will have to guide me a bit. I can see two checkboxes, 'Load DLL exports' and 'Enable RPC debugging' in Options->Debugger->Native. What kind of project do I need to make And what do I have to do next
Unable to debug: The binding handle is invalid
OgreOgre
("Project" -> "[ProjectName] Properties..". -> "Debug" -> Disable "Enable the Visual Studio hosting process")
Whats the purpose of this "Visual Studio hosting process"
Rohan Bandekar
My own bug report with an alternative workaround( ).. I've gathered some (I think all ) of the posts regarding this binding handle error. Take a look here:
http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx feedbackId=fa98bc3d-609d-4d88-81d6-e737e4e7700e
Thx,
ZAiNT
CM De Vries
Thank you so much for your help. To test native debugging:
1) File->New->Project...
2) Visual C++->Win32 Console Application
3) F10
Thanks,
Gregg
sriram.ds
mksreenivas
I don't know if it is an express problem or express restriction.
Anyone can help
eja
Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named <my pc name>. The binding handle is invlaid
But i am debugging a local application, not a remote one
KHoward
the_oldguy
Since it sounds like several people have run into this, if possible we would like to know what the real problem is. So if you have the time, could you let us know:
If you start a managed process outside the debugger (Ctrl-F5), are you able to attach to it (Debug->Attach To Process)
If not: At which point does it fail If you have a SKU that also supports native debugging, are you able to debug the native code in the process
Thanks,
Gregg
Kavitha Bhasker
davidMcKenzie
I have the same problem and no solution for now. :(
July Beta 2 VS 2005 Profesional.
Thomas Pagh
It sounds like everything is experiencing this problem for managed projects. Do you still have this problem for native projects How about attaching to a native project (example: notepad.exe)
Thanks,
Gregg
Kirk Pinneo
No, I start the process (Ctrl-F5) and as soon as I click, Debug->Attach To Process, i get the 'Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named 'COMPUTERNAME'. The binding handle is invalid.'
messagebox.
'If you have a SKU that also supports native debugging, are you able to debug the native code in the process '
I'm not really sure what you mean by this so I think you will have to guide me a bit.
I can see two checkboxes, 'Load DLL exports' and 'Enable RPC debugging' in Options->Debugger->Native. What kind of project do I need to make And what do I have to do next
Thx,
ZAiNT
Rodrigo Juarez
andrew_05
here's some more info:
http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx feedbackid=1c26f151-6455-4117-998a-41f4675fe7e7