NOVICE: Remote Debuging - What is Needed?

  • Thread starter Thread starter Peter N. Konstant
  • Start date Start date
P

Peter N. Konstant

Hello,

Thanks for reviewing my question. I have VS.NET 2003 and created a C#
SmartDevice project. I have a Windows CE device. Both units are connected
to the network. I would like to debug the application on the actual unit.
What do I have to get the remote debugging working? Can I do it over TCP/IP
or do I have to use ActiveSync?

Many Thanks to the Expert!
Peter
 
Can we please keep the questions threaded, rather than expecting someone to
remember who you are and pick up where the conversation left off? Surely
there's a reply button in whatever newsreader you're using.

You can do it over TCP/IP. You still need the toolkit that I mentioned and
you need to set the processor type. There are two more steps, however:

1. On the Windows CE device, you have to run SDAuthUtilDevice.exe (from
Platform Builder), and select the Start button.

2. On the desktop side, choose the Smart Device Authentication Utility from
the VS.NET Tools menu. Enter the IP address of the device and choose
Connect. When the connection is established, you are connected to the
device and can deploy and debug.

Paul T.
 
You need to install the Studio 2003 Add-on pack, which will include the
Smart Device Authentication utility. Run it on the PC and the device to
make a connection and you're off an running.
 
Paul said:
Can we please keep the questions threaded, rather than expecting someone to
remember who you are and pick up where the conversation left off? Surely
there's a reply button in whatever newsreader you're using.

You can do it over TCP/IP. You still need the toolkit that I mentioned and
you need to set the processor type. There are two more steps, however:

1. On the Windows CE device, you have to run SDAuthUtilDevice.exe (from
Platform Builder), and select the Start button.

2. On the desktop side, choose the Smart Device Authentication Utility from
the VS.NET Tools menu. Enter the IP address of the device and choose
Connect. When the connection is established, you are connected to the
device and can deploy and debug.
Click to expand...

Why I can do it without any add-on?
I just switch from the "IP assigned by ActiveSync" to "Specific IP"
setting the IP of my PocketPC in the device options in VS.net.
 
Zanna said:
Why I can do it without any add-on?
I just switch from the "IP assigned by ActiveSync" to "Specific IP"
setting the IP of my PocketPC in the device options in VS.net.
Click to expand...
Same with us. We took the device out of the cradle and were still able to
debug out application. Then we realized that WLAN was active and the
specific IP was still in the device settings from the last time we used the
Smart Device Authentication utility. Since then we never started this
utility again. Debugging works with every device that has its own IP
address. It seems the utility is just for people who cannot find out their
device's IP address.

Marc
 
There will still be problems, if you don't have the CPU selection utility,
with Windows CE.NET devices. Hey, it's a free download. What's the big
deal?

Paul T.
 
Paul,

no big deal. We will still use the CPU selection utility. We were just
surprised it worked. And the IP utility is not that comfortable. You have to
edit the IP address any time even if device and host PC have fixed IP
addresses. And it's a bit strange two have programs running on both systems
without knowing what they are really good for.

Marc
 
Yes, I think it's rather silly to change the way you connect to a device for
debugging from eVC to VB.NET/C#, too... I suppose that, if you have a fixed
IP address on both ends, you could probably automating the connection
process when you launch VS.NET or something (I do this for eVC connections
to our devices, but, of course that only requires something to happen on the
Windows CE end, not on both ends).

Paul T.
 
Back
Top