Is there a comparison chart between a PocketPC without CF, with CF1,
CF1+SP1, CF1+SP2 and the upcoming CF2??

As a side note, would the use of RAPI (for example OpenNETCF.org's Desktop
Communication API) require any of the CF sets or would it be runnable
without CF (i.e. on a PocketPC 2002 machine)?

/ Peter

There is a pretty fundamental difference between no NETCF and NETCF v1.0 in
that you can't run managed applications full stop. There aren't any
differences in the native APIs available though. All Pocket PC 2003 devices
and upwards have the .NETCF in ROM.

SP2 adds mostly bug fixes and some significant performance enhancements. The
only true "new" functionality is support for ForeColor and BackColor on
standard controls although there is no direct designer support for this in
Visual Studio. Because these properties were in v1.0 but not implemented
there are no API changes in SP2. SP2 also adds support in the runtime for
Windows Mobile 2003 Second Edition.

NETCF v2.0 is a significant update from v1.0 with lots of exciting new
stuff. Here is a graphical representation of the differences between v1 and
v2 (along with some new Windows Mobile specific APIs announced at MDC)

OpenNETCF's desktop library runs purely on the full framework. The only
prerequisite is the .NET Framework v1.1 on the desktop and ActiveSync (for
RAPI)

Peter

--
Peter Foot
Windows Embedded MVP
www.inthehand.com | www.opennetcf.org

Do have an opinion on the effectiveness of Microsoft Windows Mobile and
Embedded newsgroups? Let us know!
https://www.windowsembeddedeval.com/...ity/newsgroups

"PeterB" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Is there a comparison chart between a PocketPC without CF, with CF1,
> CF1+SP1, CF1+SP2 and the upcoming CF2??
>
> As a side note, would the use of RAPI (for example OpenNETCF.org's Desktop
> Communication API) require any of the CF sets or would it be runnable
> without CF (i.e. on a PocketPC 2002 machine)?
>
> / Peter
>
>

Here is the link to the diagram:-
http://blog.opennetcf.org/pfoot/Perm...c-6a3327795dff

Peter

--
Peter Foot
Windows Embedded MVP
www.inthehand.com | www.opennetcf.org

Do have an opinion on the effectiveness of Microsoft Windows Mobile and
Embedded newsgroups? Let us know!
https://www.windowsembeddedeval.com/...ity/newsgroups

"Peter Foot [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> There is a pretty fundamental difference between no NETCF and NETCF v1.0
> in that you can't run managed applications full stop. There aren't any
> differences in the native APIs available though. All Pocket PC 2003
> devices and upwards have the .NETCF in ROM.
>
> SP2 adds mostly bug fixes and some significant performance enhancements.
> The only true "new" functionality is support for ForeColor and BackColor
> on standard controls although there is no direct designer support for this
> in Visual Studio. Because these properties were in v1.0 but not
> implemented there are no API changes in SP2. SP2 also adds support in the
> runtime for Windows Mobile 2003 Second Edition.
>
> NETCF v2.0 is a significant update from v1.0 with lots of exciting new
> stuff. Here is a graphical representation of the differences between v1
> and v2 (along with some new Windows Mobile specific APIs announced at MDC)
>
> OpenNETCF's desktop library runs purely on the full framework. The only
> prerequisite is the .NET Framework v1.1 on the desktop and ActiveSync (for
> RAPI)
>
> Peter
>
> --
> Peter Foot
> Windows Embedded MVP
> www.inthehand.com | www.opennetcf.org
>
> Do have an opinion on the effectiveness of Microsoft Windows Mobile and
> Embedded newsgroups? Let us know!
> https://www.windowsembeddedeval.com/...ity/newsgroups
>
> "PeterB" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Is there a comparison chart between a PocketPC without CF, with CF1,
>> CF1+SP1, CF1+SP2 and the upcoming CF2??
>>
>> As a side note, would the use of RAPI (for example OpenNETCF.org's
>> Desktop
>> Communication API) require any of the CF sets or would it be runnable
>> without CF (i.e. on a PocketPC 2002 machine)?
>>
>> / Peter
>>
>>
>
>

Thanks!

/ Peter


"Peter Foot [MVP]" <(E-Mail Removed)> skrev i meddelandet
news:(E-Mail Removed)...
> There is a pretty fundamental difference between no NETCF and NETCF v1.0
in
> that you can't run managed applications full stop. There aren't any
> differences in the native APIs available though. All Pocket PC 2003
devices
> and upwards have the .NETCF in ROM.
>
> SP2 adds mostly bug fixes and some significant performance enhancements.
The
> only true "new" functionality is support for ForeColor and BackColor on
> standard controls although there is no direct designer support for this in
> Visual Studio. Because these properties were in v1.0 but not implemented
> there are no API changes in SP2. SP2 also adds support in the runtime for
> Windows Mobile 2003 Second Edition.
>
> NETCF v2.0 is a significant update from v1.0 with lots of exciting new
> stuff. Here is a graphical representation of the differences between v1
and
> v2 (along with some new Windows Mobile specific APIs announced at MDC)
>
> OpenNETCF's desktop library runs purely on the full framework. The only
> prerequisite is the .NET Framework v1.1 on the desktop and ActiveSync (for
> RAPI)
>
> Peter
>
> --
> Peter Foot
> Windows Embedded MVP
> www.inthehand.com | www.opennetcf.org
>
> Do have an opinion on the effectiveness of Microsoft Windows Mobile and
> Embedded newsgroups? Let us know!
> https://www.windowsembeddedeval.com/...ity/newsgroups
>
> "PeterB" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Is there a comparison chart between a PocketPC without CF, with CF1,
> > CF1+SP1, CF1+SP2 and the upcoming CF2??
> >
> > As a side note, would the use of RAPI (for example OpenNETCF.org's
Desktop
> > Communication API) require any of the CF sets or would it be runnable
> > without CF (i.e. on a PocketPC 2002 machine)?
> >
> > / Peter
> >
> >
>
>