terça-feira, 18 de novembro de 2008 04:18Hello.
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.
Todas as Respostas
terça-feira, 18 de novembro de 2008 04:46actually it requires me to connect to the home network even if the internet is not on.
terça-feira, 18 de novembro de 2008 15:07Have you not upgraded your visual studio to sp1?
By the way what name have you given to your computer?
is it 64bit?
- Marcado como Resposta Xingwei Hu segunda-feira, 24 de novembro de 2008 02:54
sábado, 9 de maio de 2009 20:24hello everybody,
I'm using VS 2008 SP1 and XP x64, having the same problem with VB, What should be done to resolve this issue ?
sábado, 9 de maio de 2009 20:42Just found the solution.
I ran a repair from \Remote Debugger\x64\rdbgsetup.exe in the DVD, and now it works.
- Sugerido como Resposta Cyanos segunda-feira, 22 de março de 2010 17:26
terça-feira, 19 de maio de 2009 15:14Thanks for the solution. I had the same problem and is now fixed. :)
terça-feira, 19 de janeiro de 2010 10:59After 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.
quarta-feira, 15 de agosto de 2012 14:35you can try also the properties, compile, and set to x86....i solved the same problem with this.
- Editado TheJocker quarta-feira, 15 de agosto de 2012 14:35
quarta-feira, 12 de setembro de 2012 21:27
I'm using VS 2012 and getting the same error. How do we fix this with VS 2012?