Remote debugging

  • Thread starter Thread starter Aaron Smith
  • Start date Start date
A

Aaron Smith

I am very new to developing applications for PocketPC. This was the
first app that I had created and it's just a really simple one at that.
I have it installed at my customer's site and we were having some
strange issues with it the other day, and I really could have used some
type of debugging capability to step through code to see where the
problem lies... Is there anything that I can do at my customer's site to
run the debugger out there? The device has wireless access and it can
be placed in a cradle, although that would be less ideal since the
problems were when he was scanning boxes out in a warehouse. What are
the options for debugging when you don't have access to the full studio?

Thanks,
Aaron Smith
 
Hi,
so, thera are not any software to allow remote debugging on Moblie Devices
?

I have similar problem - We plan to deliver some software for clients with
wareouse 400 km from our location. I don't image, that if client have some
problem, I will have to get into car and drive to him, to take a look at his
Devices and halp him with program.

On standard Windows Remote Panel form WindosXP, or VCL software, coul'd be
very helpfull. In Borland environemnts, there is possibility of remote
debugging of application.

What to do at this case on moblie devices ?
Of course, I make an assumption that device is connected to the lan.

Regards
Qubeczek
 
In theory, the type of connection established by eVC 4 to devices running
Windows CE 4.2 and earlier could be done remotely, if the debugger was
connected to the Internet and had an accessible IP address and if the device
was connected to the Internet and that connection could be used. Neither of
those things is a very common scenario, however. Does your company have a
firewall? It would be in the way. I'm not sure how long debug operations
would take, either, but I bet it would not be pleasant...

In the VS.NET case, you could establish a connection if the *device* were
connected to the Internet with an accessible IP address and the VS.NET
machine were also able to get to the network. Again, however, this isn't
something that is very common and you'd have to do the Smart Device
Authentication stuff while on the phone with the user of the device, etc.

Paul T.
 
Hello Paul,
Can you describe how to do it (eVC4)? Is it just a matter of
configuring the platform manager and use TCP/IP transport instead of
ActiveSync? And is there anything special to do on the PDA?

Thanks!
Jerome
 
Yep. I've previously posted a rather exhaustive list of things to do for
eVC 3 (or was it exhausting?). The same basic set of steps apply to eVC 4,
but the command line parameters that you need for the PDA end are somewhat
less cryptic. Basically, when you set up the eVC environment for manual
server and tell it to 'go', it starts a server program which opens a port
that you specify (*always* set the Fixed Port option, as indicated in my
previous posts). At this point, you have to make sure that there's a hole
in the firewall for that port.

On the PDA side, you have to start a program which will connect to that port
and start communications. To do that, you have to run the cemgrc.exe
program on the device with a set of parameters which specify the TCP
protocol, the IP address and port number of the PC end of the connection,
etc. When you do that, assuming the firewall on the PDA end of things will
allow the connection to that port on the remote PC, a connection will be
established and you can download, debug, etc.

Paul T.
 
Back
Top