Geek Answers Handbook

OpenNETCF 1.4 Vs OpenNETCF 2.3

I have a chance to update an outdated suite of applications that currently use .net 1.1 for the latest .NET infrastructure.

It uses OpenNETCF 1.4 to communicate with a mobile device.

Is it worth upgrading from opennetCF version 1.4 to version 2.3?

Should I expect significant hurdles / problems with this?

OR

If someone has already done the update, is it painless and helpful?

Application uses Rapi from OpenNETCF.Desktop.Communication

PDA applications run on Dell X51 and HP IPaQ computers

+6
windows-mobile compact-framework opennetcf
source share
1 answer

It depends on which parts of the SDF you are using. RAPI material is not part of the SDF at all, so it is not part of the equation of communication.

SDF 1.4 was aimed at CF 1.0. Many of them were deprecated from CF 2.0 and 3.5, and we pulled out most of these obsolete pieces because it made no sense to have functional duplications.

We have also renamed many things to be more consistent with the general .NET naming conventions.

SDF 2.3 has an entire load of bug fixes and over 1.4.

So, in the general case, the transition from 1.4 to 2.3 consists mainly of:

  • namespace is changed to use System. * where CF provided the capabilities of only the originally provided SDF
  • Class name changes for renamed classes (classes that end in "2" have been renamed to the end with "Ex".
  • changes in the code using refactored SDF fragments (during this period there have been changes in the WiFi network)
+5
source share

More articles:


All Articles