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

"John T" wrote in message
ws.com...
"JerryK" wrote in message

There are many memory leaks and other issue with the CF. Check the
newsgroup microsoft.public.dotnet.framework.compactframework for the
details. The CF is getting better, but still has a ways to go.

I've been following that group for a few months, but I wouldn't go so far
as
to say it's "unfortunate" a developer chose to use the CF. Most of the
memory issues (many reports of "leaks" are not actual leaks) I've seen
have
been due to either custom unmanaged code or poor resource management
(usually an indication of poor development habits gained in desktop
development).

I will grant you that the CF needs to improve, though. The lack of
tooltips
and context-sensitive help, for instance, are quite significant since they
are requirements for the logo program. Therefore, any CF-based app cannot
be certified on the PocketPC/Windows Mobile platform.

--
John T
http://tknowlogy.com/tknoFlyer
__________







----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! 100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---