OpenNETCF ConnectionManager, OpenNETCF.Net supported under CF2.0

  • Thread starter Thread starter Simon Hart
  • Start date Start date
S

Simon Hart

Hi,

I am correct in thinking the above will work under a CF2.0 app. I am using
1.2 of OpenNETCF. Am I also correct in thinking if I ship binaries as is
with a CF2.0 app, I will need CF1.0 runtime as well as CF2.0 for my
converted app unless of course I compile the above classes under CF2.0?

Regards
Simon.
 
Your binaries or anybody else's, will live in a process (think it is the
starting exe). Only one CF runtime will exist in that process.

If your app has dependencies on v2 code, your app will run against CF v2 and
it will need deploying to the device (not CF v1).

If your app hasn't got dependences on v2 code, it is your choice whether it
runs against v1 or v2 (configurable via a config file).

May I ask why you don't take 4 minutes to recompile your code with VS2005
(assuming you have VS2005 Standard)?

Cheers
Daniel
 
I do have dependencies on CF 2 as I want to make use of the new feature such
as HIDPI support etc. So I am guessing that shipping OpenNETCF dlls with my
v2 CF app will still work OK? if not I will just recompile the OpenNETCF
source and include the new v2 binaries.

I have found doing a conversion v1 -> v2 does not convert to the CF 2. It
seems to allow you to develop code under VS2005 but target CF1. As many new
features such as HIRES etc is not available. It seems recreating the
desginer code is required in order to make use of v2.

Regards
Simon.
 
Upgrading a v1 project with VS2005 upgrades it to v2.

The specific issue you describe of HIRES and having to recreate the designer
code may be a specific issue but in any case I am not aware of it. I am
interested, can you provide the steps to reproduce the behaviour?

Cheers
Daniel
 
Back
Top