[DUG] D2006 and compact framework

Tue Nov 21 18:59:58 NZDT 2006

For info:-

I've just completed a commercial Pocket PC project in .NET (unfortunately 
not in DELPHI).  Development for PDAs in the compact framework is satisfying 
in the end, but there can be considerable frustrations along the way!

1. Definitely use version 2 of the Compact Framework - there are many 
additions and improvements, including the addition of the serial 
communications class.

2. Make sure you apply SP1 as well - it fixes some subtle but annoying bugs.

3. Most applications will need to do some "PInvoke" calls to unmanaged code 
to provide the functionality that the CF Team chopped out from the full 
framework.  Development in Win CE provided access to a lot more needed 
functionality.

4. Some components like Microsoft's CF Tab control are so crippled as to be 
near useless for a professional application.  You will likely end up having 
to either subclass and create your own controls   or buy some third party 
controls to save time (generally a better option).

5. Beware of the differences between PDA models and manufacturers.  Make 
sure you develop/test on the target PDA for your Client.  One example is the 
difference in Bluetooth stacks but there are other subtle differences 
between devices e.g. the "path" to the CF card, serial port assignments, 
etc.

6. Unless you have access to an experienced "CF Guru" then allow 
considerably longer time for developing an application than you would 
estimate for a .NET desktop application.  The extra time is consumed in 
tasks like deployment via ActiveSync to the device for testing, resetting 
the device when it hangs, figuring out work-arounds for control or forms 
issues, posting to forums to find answers, prototyping to check out 
architectural ideas, etc.

7. Download one of the free PDA registry editors and use it.  There are also 
some "Pocket Tweak" programs for altering things like scrollbar widths (the 
latter can be important since screen real-estate is at a premium on a PDA).

8. Download a free "soft reset" program for the PDA.  You'll likely find you 
have to do this quite often during development, depending on what the 
application is.

9. There's a registry setting for ActiveSync that you can set to avoid the 
annoying pop-up window every time you "connect" to a device (i.e. plug it in 
to the cradle).

10. When looking on the web for articles relating to compact framework 
development make sure that they are for the correct version of framework 
(i.e. the one you are developing in).  Remember that there's CF1.0, CF1.x, 
CF2.0 plus service pack variants.  There are differences between versions on 
things like threading and changing controls on the main thread from a 
background thread, etc.

11. If you post to one of the Microsoft compact framework or mobile device 
forums don't expect a quick response!

Eric Apperley
Eric Apperley & Associates Limited
Consulting Engineers - Automation
Christchurch

>From: <jamessugrue at xtra.co.nz>
>Reply-To: NZ Borland Developers Group - Delphi List <delphi at ns3.123.co.nz>
>To: NZ Borland Developers Group - Delphi List <delphi at ns3.123.co.nz>
>Subject: Re: [DUG] D2006 and compact framework
>Date: Mon, 20 Nov 2006 16:51:55 +1300
>
>Doing any Mobile dev with .NET 1.1 is unpleasant. I wouldn't bother with CF 
>unless you were doing CF 2.0.
>
>
>---- Alister Christie <alister at salespartner.co.nz> wrote:
> > have a look at
> > http://bdn.borland.com/article/33798
> > I havn't got around to watching it yet.  I have one .net cf app written
> > in vs2003 (a rather unpleasant experience which I hope not to repeat).
> > I hope to rewrite the app in Delphi at some stage so it has much better
> > integration with our desktop app.
> >
> > Alister Christie
> > Computers for People
> > Ph: 04 471 1849 Fax: 04 471 1266
> > http://www.salespartner.co.nz
> > PO Box 13085
> > Johnsonville
> > Wellington
> >
> >
> >
> > Jeremy North wrote:
> > > The compiler supports CF without the need for an additional download.
> > > The IDE still doesn't support CF Form designing at design time. You
> > > can compile CF applications directly in the IDE by removing the
> > > Desktop assembly references and replacing them with the Assemblies
> > > from the Compact Framework SDK. You also need to change the library
> > > path to be <bds>\lib\cf.
> > >
> > > There is a version of the Add In for BDS2006. It is available on
> > > CodeCentral (http://cc.borland.com/Author.aspx?ID=205627).
> > >
> > > There is a newer version that isn't public yet. If you'd like the
> > > download information - email me directly. The newer version has
> > > updated Class Helpers as well as numerous fixes/enhancements to the
> > > IDE integration.
> > >
> > > The reason it isn't public yet is complicated - and frustrating
> > > (believe it or not).
> > >
> > > cheers,
> > > Jeremy
> > >
> > > On 11/20/06, Jeremy Coulter <vss at vss.co.nz> wrote:
> > >>
> > >> Does D2006 support the compact Frame work? I had some add-in that JED
> > >> from
> > >> this group wrote fro D2005, but I thought D2006 supported it now?
> > > _______________________________________________
> > > Delphi mailing list
> > > Delphi at ns3.123.co.nz
> > > http://ns3.123.co.nz/mailman/listinfo/delphi
> > >
> > >
> > _______________________________________________
> > Delphi mailing list
> > Delphi at ns3.123.co.nz
> > http://ns3.123.co.nz/mailman/listinfo/delphi
>
>_______________________________________________
>Delphi mailing list
>Delphi at ns3.123.co.nz
>http://ns3.123.co.nz/mailman/listinfo/delphi

_________________________________________________________________
Discover fun and games at  @  http://xtramsn.co.nz/kids