To my OpenNETCF friends

  • Thread starter Thread starter Jared Miniman
  • Start date Start date
J

Jared Miniman

Hi. :)

I have a bunch of OpenNETCF 1.2 assemblies referenced in a CF 2.0 project;
VS 2005 seems to want to push the *CF 1.0 CAB* file to the device each time
I deploy--could the OpenNETCF 1.2 assemblies perhaps be causing this
behavior? Is this an issue fixed with SDF v1.3?
 
Theres a bug with SDF v1.3 where it will push the SDF cab to the device
every time - this is because it doesn't register all the assemblies
correctly in the GAC, so long as you copy the missing ones e.g.
OpenNETCF.WindowsCE.Forms manually to your program folder it'll still run
okay, but you'll get this inconvenience during deploy. A patch is in the
works to fix this and other deployment issues.
However if this is occuring with the .NETCF cabs themselves this sounds like
another problem. You could try removing and reinistalling the latest SP3
runtimes and see if that cures the issue, sounds like a similar GAC issue.

Peter
 
As a follow-up, I just did ILDASM on the OpenNETCF v1.2 assemblies we're
utilizing, and sure enough, it's linking to the v1.0 of things like
mscorlib, System.Drawing, and System.Windows.Forms. So is everyone porting
to CF 2.0 (without taking each OpenNETCF assembly's source code, converting
to VS 2005, and rebuilding) out of luck?
 
The v1.3 assemblies should work fine within a v2.0 project, the references
will be handled by the runtime, there are a couple of behavioural
differences between the v1 and v2 runtimes to fix bugs which existed in v1
(e.g. GCHandle offsets) but most if not all of the code in v1.3 has been
written to compensate for this so it will check whether it needs to manually
add 4 bytes.
At this stage the installer for v1.3 is tightly tied to VS2003, so theres
not easy way to utilise it from a v2.0 project - you can either grab the
source yourself or pull the dlls off of another machine with v1.3 already
installed.

Peter
 
Peter,

I assume we will not see a "proper" SDF installer for VS 2005 until 2005
goes RTM? Perhaps later?

--
_________________________________
Jared Miniman
Accenture Mobile Solutions Group
 
I'd hope we can get one out before RTM, but as we are coding against betas
there's a chance that things will change in the run up to RTM so we will be
following a moving target. A short-term approach may be to install just the
dlls for VS2005 and leave out some of the deeper integration, we'll just
have to see how it goes...

Peter
 
Back
Top