symbol 8100 flash : framework, adoce.net, and cfserial

  • Thread starter Thread starter Bruce
  • Start date Start date
B

Bruce

hi,

need to move my app to flash.

1) .net framework itself - what cabs to load on 8100? how do I tell
which I'm using?

2) using adoce.net - how to reinstall on cold boot? I saw posting on
inthehand forum that included a variety of manual settings in inf
file. if I run the adoce cab file independently, do I still need those
inf changes?

3) cfserial - will there be any registry settings to reload? I will
be reinstalling my app from cab on cold boot - is this sufficient to
drag along cfserial?


thanks very much!
 
Hi, Answers inline:

Bruce said:
hi,

need to move my app to flash.

1) .net framework itself - what cabs to load on 8100? how do I tell
which I'm using?
Click to expand...

My understanding of the 8100 is it is an ARM based Pocket PC 2002 device so
you will require "netcf.core.ppc3.ARM.cab" version of the Compact Framework.
2) using adoce.net - how to reinstall on cold boot? I saw posting on
inthehand forum that included a variety of manual settings in inf
file. if I run the adoce cab file independently, do I still need those
inf changes?
Click to expand...

The ADOCE .NET Wrapper uses the ADOCE ActiveX control, as well as the files
that make up the wrapper itself. You can install the ADOCE control either
through a custom CAB file as described or use the ready made separate CAB
file which installs and registers the ADOCE 3.1 control on the device. Again
you will need the ARM version of this cab file.
The wrapper consists of a Native Dll and a managed dll. Using the latest
version (1.3) these will both be incorporated into your application cab
automatically if you are using the Visual Studio "Build Cab" feature.
3) cfserial - will there be any registry settings to reload? I will
be reinstalling my app from cab on cold boot - is this sufficient to
drag along cfserial?
Click to expand...

CFSerial is a purely managed assembly so you can simply place it in your
application folder. AFAIK it uses no registry settings or pre-requisite
native dlls.

Peter

--
Peter Foot
Windows Embedded MVP

In The Hand
http://www.inthehand.com
 
Back
Top