Running on both Net and Netcf

[Guest]

My task is to move an instrument controller module (called an ICE implemented
on a ICE.dll) down into a Pcb that supports Netcf. At present at the Desktop
level it uses Remoting to communicate with another application.

After reading various articles, the Msdn and this newsgroup I believe that
Sockets would be a good choice for us since Remoting is not supported on the
Netcf.

We manufacture analytical instruments for chemists (ICP's, Atomic Absorption
spectrometers, etc). Each will include a WinCe with an ICE to control it.

There can be 1 to N ICE's on each Pcb (though it will usually be 1). All
ICE's are controlled by a central component called the MIM (implemented as
MIM.dll).

The ICE's will only communicate with the MIM not with other ICE's.

On team would like the ICE's and the MIM to run on either Netcf or Net.
Since the projects and Reference's are different for Netcf and Net it would
appear to mean that we will have to have two source code tracks.

The question is it possible for Exe's and Dll's meant for WinCe Netcf to run
on the desktop as well as on the WinCe pcb?

If not is there another away to avoid maintaining two separate but
synchronized code bases?

Thanks.

--John Olbert
(e-mail address removed)

 

[Paul G. Tobey [eMVP]]

Really no fair doing it three times, although you are contributing to my
response count for the day!

Paul T.

 

[Guest]

My apologies. Each of the three were separate questions though the context
for each was the same. In the future I will include all questions in one. I
thought it would make it simplier to submit each separtately. Sorry.
--
John Olbert

Really no fair doing it three times, although you are contributing to my
response count for the day!

Paul T.

 

[Daniel Moth]

For sharing code on both platforms:
http://www.danielmoth.com/Blog/2004/09/share-code-if-fullframe_17.html

Cheers
Daniel

 

[stu]

I have done this, but not very much. My suggestion is to have a .dll
file with most of the framework (full/compact) independent stuff in it;
this is typically most of the actual doing-stuff code. Then have 2
GUIs (if you need guis). Create the 2 GUI projects and then just
import the dll into both. The biggest problem I've had with full/cf
apps is that certain interface objects are different. If you build it
correctly, the agnostic code should be easily callable from both GUIs.
In addition to the GUI code, put any platform specific calls in the GUI
code section and just use delegates to pick the right method call.

I don't know how "correct" that is, but it worked for what I needed it
to do.

stu =)