Re: Which of these should I use for my application?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



On Tue, 2 Oct 2007 22:57:00 -0700, may <may@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

Thanks for the replay
you said your using eVC3 so your executables work on all PPCs. Is this the
only way to do that ? or there is also other tools to target all PPCs?

It's the only way I've tried.

I've seen ways to tweak executables made with a new SDK so they run on
older versions of the operating system. But nothing I would try. And
if you do use such an approach, you need to keep checking to make sure
you haven't included any functions that are unsupported on the old
version.


Thanks again

"r_z_aret@xxxxxxxxxxxx" wrote:

On Sun, 30 Sep 2007 22:32:01 -0700, may
<may@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi,
I'm developing a pocket pc software (windows CE 6.0) and am not sure which
tools to use. i'm realy beginner in this field.
Would you recommand using visual studio 2005? or Is it okay to use eVC++?

To expand/counterpoint earlier replies:

A very definite maybe to both questions.

If you need to support older platforms (earlier than WM 5) you will
need to use eVC.

If you need to use a specialized platform with its own SDK, you will
need to use whatever IDE/compiler that SDK requires.

If you _need_ to debug directly on WM 5 devices, you will need to use
VS 2005.

If you want much support from Microsoft, you probably need to use
their current products, and that means VS 2005.

I'm sure some folks have tried eVC 3, eVC 4, and VS 2005 and have
their preferences. Maybe if you try at least two, you'll have a
preference, too.

I generally use eVC 3 and build for the original Pocket PC. That means
my executables work on _all_ Pocket PCs. But it also means I can't
debug directly on newer Pocket PCs. Once in a while, I use eVC 4 so I
can debug on a Pocket PC 2003. I've tried VS 2005, but don't really
use it.



Thank you in advance

-----------------------------------------
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


-----------------------------------------
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
.



Relevant Pages

  • Re: Which of these should I use for my application?
    ... you said your using eVC3 so your executables work on all PPCs. ... I'm sure some folks have tried eVC 3, eVC 4, and VS 2005 and have ... I generally use eVC 3 and build for the original Pocket PC. ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: "Platform manager cannot create the communication streams needed by the debugger" error
    ... >I can successfully build my app, ... described a work-around for a known problem with eVC 4. ... >I'm using Active Sync version 3.8, and the target Pocket PC is running ... original Pocket PC platform. ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: Some questions; SHMenuBar, multilingual prog
    ... >>> applications that run on a Pocket PC 2003, but you will not be able to ... It worked under eVB, but not eVC. ... When I try to start EVC, it says something like "SDK not ... >>Emulator showed a 1024x768 environment, the OS looked like a handheld ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: Visual Basica nd Pocket PC
    ... If you installed the tools in the order you described, eVC 4.0 should work. ... > i.e. Mobile Pocket PC 2003 SDK. ... > "Maarten Struys, eMVP" wrote in message ...
    (microsoft.public.pocketpc.developer)