Remote Debugging in Visual Basic 6.0

[acects]

Hello everybody!!

I want to debug my visual basic 6.0 application on the remote computer.

For example:
The application and the visual studio 6.0 are existing in computer nr.1, but the result's from debugging I want to see on another computer for example computer nr.2, which is connected on the same LAN network.

please help

[jcis]

Welcome to the forums

What about connecting to the remote machine via remote desktop? The only way to debug in VB is running the App in the IDE, so you need to access and control the other computer Desktop.

[acects]

Thanks, but i haven't still used the remote desktop. Concretly the problem is:
The computer1 has Windows XP professional, Visual Basic 6.0 and my application made in VB 6.0
The computer2 has only Windows 7 Ultimate.
Can I see the application results while debugging on the computer 1.

[techgnome]

short answer: No
Longer answer: No you can't.
Even longer answer: you can only really debug on the machine where VB is installed. Even if VB was installed on the other machine, you would then need to be on that machine either physically or via Remote Desktop.

-tg

[acects]

Thanks again

I am just researching this answer, because I succeed to remote debug with Visual C++ 6.0 on another machine with windows 7. I used the remote debug monitor msvcmon.exe. Is there such tool in Visual Basic 6.0?

[jmsrickland]

short answer: No
Longer answer: No you can't.
Even longer answer: you can only really debug on the machine where VB is installed. Even if VB was installed on the other machine, you would then need to be on that machine either physically or via Remote Desktop.

-tg

If I have two computers, computer1 has VB installed and the VB app I want to debug. Then I go over to computer2 and use remote desktop to connect to computer1 are you saying that I cannot debug the VB app from computer2 because it does not have VB installed? Seems like that defeats the purpose of remote desktop. I thought remote desktop actually allows you to use the desktop of the other computer and it's applications.

[techgnome]

no... that's not what I said at all... I assumed that the OP wanted to sit on computer 1, where the app is.... and VB is installed.... and somehow debug the app running on computer 2. The only way I know how to do that is to use RDP to remote in, but then it's like you're sitting there on computer 2... and since it doesn't have VB installed, debugging on it is pointless.

In the scenario you gave, YEs, you CAN debug the app on computer 1 using RDP, because computer 1 has the tools... when you RD in, it's like you're physically on the box...
"The application and the visual studio 6.0 are existing in computer nr.1, but the result's from debugging I want to see on another computer for example computer nr.2" -- I interpreted this to mean that while sitting physically at computer #1, he wants to debug the app running on computer #2.

-tg

[jmsrickland]

So, the bottom line is

On computer2 (does not have VB on it) which is logged into computer1 (does have VB on it) via RDT I can debug VB on computer2 using the VB IDE on computer1?

The OP says

The application and the visual studio 6.0 are existing in computer nr.1, but the result's from debugging I want to see on another computer for example computer nr.2, which is connected on the same LAN network.

In this case, No. You can't debug on computer1 and see the results on computer2. You would have to do the debugging on computer2.

Do I have this correct from what you have said?

[techgnome]

"On computer2 (does not have VB on it) which is logged into computer1 (does have VB on it) via RDT I can debug VB on computer2 using the VB IDE on computer1?" -- depends on how pedantic you want to be about it... on the surface... yep, sure, that's the true. but if you want to be exacting, then no... because once you RDP into the second computer you are for all intents and purposes on that second machine and the first one doesn't really exist.

I think we have a couple of barriers in the way here. The first and foremost is a clear understanding of what the OP wants and is trying to do. Once we get that solved then we can figure out if it's possible.

-tg

[jmsrickland]

Well, that answers the question no matter how pedantic I am.

[acects]

http://www.codeproject.com/Articles/...-step-in-the-O

This is the link where I find solution about remote debugging with visual C++ 6.0. I am asking is it possible this procedure in Visual Basic 6.0 because I am beginner with Visual Basic 6.0, but I am experienced with Visual C++.

Here is the problem again:

Computer 1
-where I am sitting physically and debugging with breakpoints.
-the Visual Studio 6.0 is on this computer
-the application which i debug is also on this computer

Computer 2
- have only Windows 7 and it is on same LAN network with first computer (both computers can see each other through network).
-this computer shows just the results for example: if i press F10 on first computer, on second computer shows the console printing for example "Hello World".

This is 100% possible with Visual C++6.0

[jmsrickland]

Since you already know it is 100% possible with VC++ wouldn't you also think the same for VB? Why don't you just try it and see if it works?

tg stated,

"...because once you RDP into the second computer you are for all intents and purposes on that second machine..."

This tells me that you should be able to see the results on computer2 even though you are debugging on computer1 but I do not know this for a fact.

[dilettante]

Compile Tab (Project Properties Dialog Box)

Create Symbolic Debug Info — Generates symbolic debug information in the executable or DLL file. An executable file created using this option can be debugged using Visual C++ or debuggers that use CodeView style of debug information. Setting this option generates a .pdb file with the symbol information for your executable.

Create Symbolic Debug Info

Generates symbolic debug information in the compiled executable file.

Programs compiled to native code using this option can be debugged using Visual C++ (5.0 or later) or another compatible debugger. Setting this option will generate a .pdb file with the required symbol information for use with compatible symbolic debuggers.

As far as I know you can use the Visual Studio debugger or tools like WinDbg.

A word for WinDbg

For your own code you’re responsible for building the symbol files (usually .PDB program databases) by setting the right flags on the compiler or choosing the right configuration in a project (this is true for VC++, VB6 and all the .NET languages). This will give you full private symbols.

Note that this is not IDE debugging as such though.

[acects]

Well, the need to do that is because when you debug some GUI application you can not see always the graphical elements and windows while debugging. With the remote debugging I can always see the code and the application. Also it is used for some graphical applications where this debugging is so important for developer to see if everything is good at the right moment.