debugging on device

[Geoff Callaghan]

YAHOOO! that's what I needed to know. For some reason, TOOLHELP.DLL was not
on my device. I copied it there, and everything deployed and ran. I really
can't thank you all enough for your help.

 

[Geoff Callaghan]

Thanks, but the guy above, nzpcmac, pointed out a place to go. Turns out I
didn't have TOOLHELP.DLL on the device. It's working now...thanks for all
your help. I couldn't have gotten this far without you guys!

Double check the proxy ports thing, as suggested in the other thread. If
it's not that, I'd start with reinstalling...

Paul T.

Yeah, that works fine. Curiouser and Curiouser. Is there a debugging
library
I'm not downloading?

OK, that's useful information. Can you, from the VS.NET IDE do a Run
without Debugger operation (I don't recall the specific menu item

name),
and

have the application run?

Paul T.

OK, I tried that...I put a breakpoint on the Application.Run(New Form1())
command of a brand new empty application, just a form and a lable. I
hit
run, and it said it was deploying...then it said "Launching
application"...then it stopped, as if I'd never hit start in the first
place. No breakpoing, no nothing. I even tried starting it with a "step
into", and the same thing happens.

My initial application was fairly complicated, with several support
libraries. The libraries all install fine. Even the program ends up

on
the

machine.




"Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT
com>
wrote in message OK, that's a different problem of some sort. Are you trying this

with
a

very minimal application, or is this something that references extra
assemblies, etc.? The best thing to try first would be a
wizard-generated
Smart Device Application with no code added to it. Set a breakpoint in
the
main routine and see how that runs. Either way, that should tell us
something useful.

Paul T.

I am telling to start. It just doesn't start. It even says "launching
application....", but there is no launch.


"Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT
com>
wrote in message That depends on what you tell the environment to do. If you tell
it
to
"deploy", that's what it does. There's no reason to expect that to
start
the program, too. If you tell it to Start, then it will start...

Paul T.

OK, It looks like I have everything set up right. When I run the
program,
it
installs and deploys everything to the device. But shouldn't the
program
then run? The program is copied to the device, and if I run it on
the
device
it works, but I had assumed that the program would start up by
itself,
so
that I could set breakpoints and step through it if necessary.


"Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT
com>
wrote in message You have to read my previous message...

"If you're not using a PPC device, you have to get the Windows
CE
Tools
for
VS.NET from www.microsoft.com/downloads, and set the right CPU type
(a
couple of new tools appear on the VS.NET tools menu). After that,
you
should be able to deploy."

Yes, other than setting up a few things as listed above, all you
have
to
do
is establish a working ActiveSync connection (it does have to

be
a

working
ActiveSync connection, not just connect the cable up and hope
for
the
best),
and you should be able to deploy to the device.

I guess before I make some sort of blanket statement I should
verify
that
you *are* running a Windows CE.NET 4.2-based device, right?

Paul T.

Where do I do that? I don't see any options for that. I know when
I
copy
the
program over...which works fine, by the way...the program runs
perfectly.
It
wouldn't do that if I was using the wrong processor.

I feel like I"m missing a step here that everyone else

thinks
is

obvious,
so
they're not mentioning it. That's been happening to me pretty
regularly
since I started working with the compact framework. Are you guys
saying
all
I should have to do is choose the Device instead of the Emulator
in
the
dropdown, connect to my device with a USB cable, and hit

run,
and

my
program
should deploy and run on the device? That's what I'm doing,
and
it
says
it
can't connect.

I didn't write the OS...is it possible there is something
wrong
there?


"Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no
spam
DOT
com>
wrote in message When you start using a real device, if it's based on Windows
CE.NET,
as
opposed to PPC, you have to tell it what processor you are
using,
yes.

Paul T.

I have those tools installed, and I have chosen "Windows CE
.NET
Device".
I
have been using Windows CE .NET (emulator) without
problems.
Is
that
what
you are talking about? It doesn't work. Or am I supposed to
tell
it
what
processor I'm using somehow?


Is this a PPC or Windows CE device? You have to have
selected
the
appropriate CPU from Windows CE Tools.

Dick

--
Richard Grier (Microsoft Visual Basic MVP)

See www.hardandsoftware.net for contact information.

Author of Visual Basic Programmer's Guide to Serial
Communications,
4th
Edition ISBN 1-890422-28-2 (391 pages) published July 2004.
See
www.mabry.com/vbpgser4 to order.