Re: Newbie: CE4.2 migration to CE 6.0 - what tools to use?



One last thing - you should check out CEAppCompat Tool. Check here: http://channel9.msdn.com/posts/mikehall/Application-Compatibility-Migrating-Windows-CE-50-Application-to-Windows-Embedded-CE-60/

--
Michael Salamone
Entrek Software, Inc.
www.entrek.com


<r_z_aret@xxxxxxxxxxxx> wrote in message news:4hsi255ap8lri9on6cl94qovftv2q6tgpv@xxxxxxxxxx
On Fri, 5 Jun 2009 06:53:01 -0700, HyperActive
<HyperActive@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi,
I have a very simple native C++ DLL (a "plugin" for a 3rd party app) that
I'm building for WinCE4.2 using embedded VC++ 4.0. Now I need to build this
code to run on a WinCE 6.0 x86-based platform. I gather that this is supposed
to be possible with VS2005 (which I have running on my Vista machine) by
creating a "Win32 Smart Device Project". However, when I do this I only get
to select a "Smartphone 2003" or "Pocket PC 2003" platform. Just where do I
get the right platform SDK for x86?
We have a MSDN subscription, is the SDK included in there somewhere? I
couldn't find it. Or do I have to pay extra money for this? Am I completely
barking up the wrong tree here?

I normally develop C# apps for WinXP, so this whole WinCE world seems pretty
convoluted to me. Any help would be appreciated

Yep, "convoluted" is a pretty good description.

I'll add a bit of a counter to previous posts. If you really, really
can't get the correct SDK for your target, then you might succeed
anyway.

I would start by seeing how well the DLL you build with your current
tools work on the new platform. If the DLL uses only functions and
features common to both platforms, you have a good chance of success.
If you're not quite that lucky, you might have a small enough number
of problems that you can work around.

If that doesn't work, you can choose an available SDK for a target
that's as close as possible to the actual target. This will almost
certainly _not_ be the Standard SDK, which is almost always more
bother than nothing (note: I'm about the only person around who is
even this nice to it). If you're very lucky, the result will work. If
you're not quite so lucky, you'll have a small number of problems you
can work around.

If neither of those work, you might yet succeed if you tell us
(collective, not imperial) what more about the actual target. Someone
(probably not me) may know enough about it to provide a better
approach.

-----------------------------------------
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 400
Boston, MA 02116
www.penfact.com

.



Relevant Pages

  • Re: Newbie: CE4.2 migration to CE 6.0 - what tools to use?
    ... code to run on a WinCE 6.0 x86-based platform. ... is the SDK included in there somewhere? ... you can choose an available SDK for a target ...
    (microsoft.public.windowsce.embedded)
  • Re: eMbedded Visual C++ lock up
    ... Sometimes if you install an SDK you need to reboot before you try to ... I think it has to do with whether the Platform Manager was ... > I've got a boot loader running on our ARM target and can download an OS ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Debug
    ... Yes, if you're building the platform, you are responsible for building the ... SDK, since only you know what's in the image. ... >> tool bar from Pocket PC Emulator to Pocket PC Device and, if necessary, ... >> change the target processor to the right one for the device and rebuild. ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: eVC4 target platform missing
    ... Standard SDK is probably not the right SDK for any platform at all. ... Where do I find the right SDK for my target device? ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: Adding SDK
    ... on Platform Biulder but now I have another one... ... You should see your new SDK platform ... I've built SDK and I've run the .msi file. ... file I can't include it on .bib file as I did with usb drivers! ...
    (microsoft.public.windowsce.platbuilder)

Loading