JerryK wrote:
I just think it will take time to shake out .Net in general, and CF in
particular. I agree that many of the memory issue are the results of
poor
resource management. Unfortunately an environment with a GC tends to let
programmers thing they can forget about explicitly managing resources.

I am still using the older C++ compilers for my PPC work. Still works,
still requires a lot of steps, but the code it tight and runs very fast.
What sort of dev environment are you using?

Jerry,

While this is probably not the best forum in which to discuss the merits of
the Compact Framework, I'd like to add a little to this thread and how it
helped in the development of WingX.

The most obvious advantages a no bad pointers, no leaked memory, no
crashes! These become especially important on handheld devices where leaked
memory and crashes are unacceptable. In addition, we believe our
development time is very much shorter using C# over C++ and this allows us
to get new features to customers in the shortest time. Moreover, since we
ship one EXE for all platforms, we reduce potential bugs on the numerous PDA
platforms; i.e if your PDA has the Compact Framework, WingX will run on it
irrespective of the CPU type - the same cannot be said for C and C++.

The first release of the CF was in pretty good shape, and Microsoft has
since released Service Pack 1 (downloadable from
http://www.hiltonsoftware.com/Download.html) to fix several bugs and improve
performance. In fact, this release will be pre-installed in Pocket PC 2003
so the newer PDAs, phones, and other devices will have the CF pre-installed.

We have found the Compact Framework to be very solid, and we have yet to
discover any leaked resources or other major problems.

Thanks,

Hilton
Hilton Software
http://www.hiltonsoftware.com