Porting WIN32 App to CE.

Hi All,

We currently have a client-server application written in Win32 and we're in
the process of trying to create a slimmed down version of the client
software for the Pocket PC. Our application is a fair size, and uses a few
in-house developed DLLs for drawing areas etc. We want to be able to use
code contained in these .DLLs on our Pocket PC app to avoid multiple copies
of the same code in two projects. We're using VS2003.NET for the Win32
development, and eVC 4.0 for the PPC stuff.

Has anyone been in these shoes before? How have they solved the problem?

I thought of creating a similar .DLL in my PPC application, and actually
link in the sources files from the original.DLL while adding #ifdefs to the
.DLL to include functions that I require, then compile them using the evC
compiler, realizing that not all the calls we make the .DLLs will be
available in the PPC environment. This could be quite messy, but would
eliminate the maintenence issue.

I realize that some of the calls that the Windows .DLL will make, will not
be available in the PPC Edition. We will need to address these individually
I think.


Any suggestions? Thank you very much.

Mike

r_z_aret
Wed Jun 21 15:45:33 CDT 2006

From the time I started my current job 7 years ago, my primary target
has been Windows CE, but I've done most testing under "big" Windows. I
share source code across "big" Windows and all the CE platforms I
support. I've been conscious of the differences from the beginning, so
have had time to avoid differences and to isolate most differences to
library code (so application code is mostly "neutral"). That's left me
with a relatively few #ifdefs. My very rough estimate is that 80% of
the library code and >90% of the application code is shared by all
platforms.

Characters are a big "gotcha". Windows CE is _heavily_ biased towards
UNICODE. If you don't understand this statement and its implications,
use google to look up unicode in one of these newsgroups.


On Wed, 21 Jun 2006 10:50:34 -0400, "Mike Doner" <doner@obtain.com>
wrote:

>
>
>Hi All,
>
>We currently have a client-server application written in Win32 and we're in
>the process of trying to create a slimmed down version of the client
>software for the Pocket PC. Our application is a fair size, and uses a few
>in-house developed DLLs for drawing areas etc. We want to be able to use
>code contained in these .DLLs on our Pocket PC app to avoid multiple copies
>of the same code in two projects. We're using VS2003.NET for the Win32
>development, and eVC 4.0 for the PPC stuff.
>
>Has anyone been in these shoes before? How have they solved the problem?
>
>I thought of creating a similar .DLL in my PPC application, and actually
>link in the sources files from the original.DLL while adding #ifdefs to the
>.DLL to include functions that I require, then compile them using the evC
>compiler, realizing that not all the calls we make the .DLLs will be
>available in the PPC environment. This could be quite messy, but would
>eliminate the maintenence issue.
>
>I realize that some of the calls that the Windows .DLL will make, will not
>be available in the PPC Edition. We will need to address these individually
>I think.
>
>
>Any suggestions? Thank you very much.
>
>Mike
>

-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).

Robert E. Zaret, eMVP
PenFact, Inc.
20 Park Plaza, Suite 478
Boston, MA 02116
www.penfact.com