Starting with the CompactFramework

  • Thread starter Thread starter Zanna
  • Start date Start date
Z

Zanna

Hi all!

Just a question: I don't have the VisualStudio 2003.
Can I write applications for the compact framework using the compilers
for the complete framework?

Thanks
 
The link at the bottom of that topic requires no third party software.
You'll have to compile with the command-line, but you can write the code
with anything - even notepad.
 
The link at the bottom of that topic requires no third party software.
You'll have to compile with the command-line, but you can write the code
with anything - even notepad.
Click to expand...

Maybe I'm wrong, but my problem is:
- I installed the CompactFW on the PocketPC (2002)
- I compiled the "hello world" with the command line explained in the link
- I copied the exe on the pocketPC (\programs)

But when I click on it it does nothing.

Why?
 
Run it in the debugger from VS.NET 2003 and set a breakpoint in the
constructor for your main form. Does it get there?

Paul T.
 
And now you see the value in actually buying a tool that has debugging
support.
 
Paul G. Tobey said:
Run it in the debugger from VS.NET 2003 and set a breakpoint in the
constructor for your main form. Does it get there?
Click to expand...

As I said in my first post I don't have VS2003.

But with this reply I understand that my procedure for making a CFw app is
(theorically) right.

right? :)
 
And now you see the value in actually buying a tool that has debugging
support.
Click to expand...

I know it, but, obviously, my chiefs need to view something before to buy
something >:)
 
I *can* think of other ways to get information about what's going wrong, but
none nearly as *easy and reliable* as using the right tool for the job, no.

You might, if you are the OS developer, capture the serial debug output
messages from a debug version of the OS and see what's going on there
(exception, assert failure, etc.)

You might also use the eVC debugger to watch the .NET CF process run and see
if you can capture the exception, if there is one, that way.

As Chris suggested, it's a *very* short-sighted position to avoid spending a
few hundred dollars, costing you, in the mean time, days of work that is
totally useless in the long term.

Paul T.
 
How did you copy the EXE? Through Explorer? I had the same problem. Try
letting ActiveSync handle the copying.

When I copied the EXE into the "My Documents" folder that is used by
ActiveSync, and then let ActiveSync copy the EXE into my PocketPC, then the
EXE launched and ran the way it is supposed to.
 
Back
Top