I am assuming your app is compiled against CF 2 and you are using PPC 2003 SE
or onwards as these devices already contain CF1 in ROM.
So..the easiest way to detect if CF2 is installed on your device is to check
the .unload file exits for CF2. Each CAB deployment generates an .unload file
which is the name of the manufacturer and description of the application
combined.
You need to check for the following file:
\Windows\Microsoft .NET CF 2.0.unload
If it doesn't exist, you need to fire the WCELOAD.exe passing it the CF2 CAB
file before you can load your app.
Simon.
> Hello,
>
[quoted text clipped - 11 lines]
>
> drumred
drumred - 17 Mar 2007 12:52 GMT
Is there a detailed writeup of what needs to occur on load. CF
incompatibilities should be a fairly common occurrance on app deployments.
- What if there isn't enough memory for cab?
- What if cf version and device aren't compatible?
- Low storage memory during install?
- Security setting prevent intall (WM5)?
- A managed app is running?
> I am assuming your app is compiled against CF 2 and you are using PPC 2003 SE
> or onwards as these devices already contain CF1 in ROM.
[quoted text clipped - 27 lines]
> >
> > drumred
Simon Hart - 17 Mar 2007 13:44 GMT
This is no different from the desktop, you have to handle this yourself.
There is no magic API you can call that handles these potential issues,
unfortionately ;(
Simon.
> Is there a detailed writeup of what needs to occur on load. CF
> incompatibilities should be a fairly common occurrance on app deployments.
[quoted text clipped - 36 lines]
> > >
> > > drumred