Tuesday, November 18, 2008 4:18 AMHello.
I am working with visual studio 2008, developing a simple windows form app. in VB. but a very weird situation has presented itself (at least I think its weird).
When I try F5 or any other way to start the debugger I get this message:
"Error while trying to run project: Unable to start debugging.
The debugger cannot connect to the remote computer. This may be
because the remote computer does not exist or a firewall may be
preventing communication to the remote computer. Please see Help
Needless to say, Help is Helpless.
The weird thing about it is that this only appears if my computer is not connected to the home network and only in VB. When I try to debug on any other language it works fine, or if I connect to the network then VB debugs fine.
Can someone help me? I do not think I am using a remote debugger.
Tuesday, November 18, 2008 4:46 AMactually it requires me to connect to the home network even if the internet is not on.
Tuesday, November 18, 2008 3:07 PMHave you not upgraded your visual studio to sp1?
By the way what name have you given to your computer?
is it 64bit?
- Marked As Answer by Xingwei Hu Monday, November 24, 2008 2:54 AM
Saturday, May 09, 2009 8:24 PMhello everybody,
I'm using VS 2008 SP1 and XP x64, having the same problem with VB, What should be done to resolve this issue ?
Saturday, May 09, 2009 8:42 PMJust found the solution.
I ran a repair from \Remote Debugger\x64\rdbgsetup.exe in the DVD, and now it works.
- Proposed As Answer by Cyanos Monday, March 22, 2010 5:26 PM
Tuesday, May 19, 2009 3:14 PMThanks for the solution. I had the same problem and is now fixed. :)
Tuesday, January 19, 2010 10:59 AMAfter spending days looking for the proverbial 'silver bullet', you have solved my problem!
Thank you Charnet3D :)
BTW, I encountered this problem while converting a C#, .Net 3.5, Forms application over to Visual Studio 2008, in a Windows 7 64-bit platform.
Wednesday, August 15, 2012 2:35 PMyou can try also the properties, compile, and set to x86....i solved the same problem with this.
- Edited by TheJocker Wednesday, August 15, 2012 2:35 PM
Wednesday, September 12, 2012 9:27 PM
I'm using VS 2012 and getting the same error. How do we fix this with VS 2012?