Re: Trying to wrap my head around WinCE development process

Tech-Archive recommends: Speed Up your PC by fixing your registry

assuming you solved your boot and image build trouble, getting back to the
original question : How to debug an application on CE :

Run your OS (release or ship version) on the target locally (so no (KITL)
connection to any host required). Copy a couple of tools onto your target
system : Conmanclient2.exe and CMAccept.exe. Run them in that order.
(search this group on where to find those tools)
Now go to your development system VS2005, and look for 2 buttons in your
menu-bar, one connects to the target, and it's neighbour sets up the
connection.
First set up the connection, there are several options, I usually use TCPIP
(if you have that). Set up the parameters (mainly target-IP, which you can
get from the target-taskbar icon, or use another tool on the target). After
this is setup correctly, press the connect button, and it should connect.
(this can take some messing around before it works, including IP-tools
(ipConfig/Ping) and cmd-box in the target image might help here).
If the connection succeeds, you can now deploy, and debug the same as you
would normally when developping an app for your host machine (XP?) . (by
pressing F5 it will download (deploy) and run your application)

The TCPIP connection does not require KITL. If you donot have TCPIP, you
need one of the other connection methods (activesync?). But the basic Idea is
the same, once you get a debug connection up and running , you can debug as
normal.

This complaining about activesync is nonsense, you dont need it, I also saw
this many times, not sure why it says this. There probably is some other
problem, for which it has no specific error-text, it means to say : "I cannot
connect" (AFAIK)

There is a registry setting that allows you to skip the CMAccept tool, I
forgot wat is called, but you should be able to find it in this group
somewhere. Also I think one of these connect-tools times out after beeing
unconnected for a few minutes, so beware of this, you can search a long time
for nothing if you forget this.

Kind regards,
Rob.












"ajcrm125" wrote:

Ok... finally got an image built and loaded up on the device. Turns
out I had KITL enabled so everytime I tried to download an OS image
and run it, it was trying to talk to the debugger? (MIke Hall helped
me out here).
I'm still not clean on how to actually hook up a debugger to this
thing but at least it has an image and is booting up in CE.

So I created a simple "Hello World" app in VS2005 and want to debug on
the device. So I followed these steps:
http://msdn.microsoft.com/en-us/library/ms228708(VS.80).aspx
but in doing step "To prepare Visual Studio for connecting, #4", I
noticed under "Bootstrapper" it has ActiveSync selected.... and theres
no other option. So I continue through the steps and then finally try
"Tools-> Conect to Device" or even "Debug->Start Debugging" and both
of them cry out that ActiveSync is not installed.

:-(


.

Quantcast