Re: EVC3, EVC4 or VStudio 2005?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I originally wrote a prototype of our product for PocketPC 2003 using EVC4.

Later, I wanted to build it using VS2005 and also build for WM5.

The PocketPC 2003 SDK is included in the installation of VS2005, so I
thought I could build right out of the box.
Alas... The SDK included is the same one that I had downloaded earlier for
my work using EVC4, with which it builds fine. But, the C++ language of
VS2005 has undergone some "breaking changes", and the included SDK has not
been updated, so sme of the code in some of the header files don't compile.

Fortunately, the SDK for WM5 conforms to the new C++ language, but this SDK
is not included in the VS2005 installation. I ended up having to copy six or
seven header files from the WM5 SDK into the PocketPC 2003 SDK in order to
get it to build correctly again. A windiff on these headers learned that the
only difference between the PPC2003 and the WM5 version has to do with these
C++ language changes, so I could do this quit safely, at least for these six
files.

I found it quite disappointing that an SDK included in the VS2005
installation does not conform to its own syntax rules...

Regards,

Etienne


"AliR (VC++ MVP)" <AliR@xxxxxxxxxxxxx> schreef in bericht
news:DKvph.26574$QU1.11102@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Everyone,

I have to maintain 2 programs one is PocketPC 2003 app and the other is
WinCE application. In the past the Pocket PC program was compiled using
evc3 and the WinCE was created and compiled using evc4.

I have just had to rebuild my development computer and I can't compile
either one of the projects. (I can't seem to get all the pieces
together!).

Anyway, I tried to open the PocketPC project (evc3) in VS2005 put it
wouldn't compile there either. wcesock.h was missing.

Anyway, before I get too deep into this conversion, I wanted to know which
compiler I should use. Should I convert the two program to VS2005?

Thanks
AliR.




.

Relevant Pages

  • Re: EVT 3.0 2002 edition no connection to device?
    ... The most possible problem with this, is that you are using the wrong SDK ... you are using a pocketpc, please be aware that pocketpc 2002 and 2003 ... If you are using a SHARED mfc dll, may be you have an older dll version ... If you can compile your software on a similar platform ...
    (microsoft.public.pocketpc.developer)
  • Re: EVC3, EVC4 or VStudio 2005?
    ... the SDK is a bad fix, as anyone who wants to use the project has to modify ... project - that should compile fine - then diff the two project files and see ... In the PocketPC2003 SDK that is in VS2005 there is a C++ header file ... Looking at the WM5 SDK, in the same header file "vector", this file is ...
    (microsoft.public.pocketpc.developer)
  • Re: EVC3, EVC4 or VStudio 2005?
    ... released using the PPC 03 SDK and I've seen no ... I wanted to build it using VS2005 and also build for WM5. ... The PocketPC 2003 SDK is included in the installation of VS2005, ... I have just had to rebuild my development computer and I can't compile ...
    (microsoft.public.pocketpc.developer)
  • Re: EVC3, EVC4 or VStudio 2005?
    ... released using the PPC 03 SDK and I've seen no ... The PocketPC 2003 SDK is included in the installation of VS2005, ... for my work using EVC4, ... I have just had to rebuild my development computer and I can't compile ...
    (microsoft.public.pocketpc.developer)
  • Re: EVC3, EVC4 or VStudio 2005?
    ... using the PPC 03 SDK and I've seen no problems at ... I wanted to build it using VS2005 and also build for WM5. ... The PocketPC 2003 SDK is included in the installation of VS2005, ... I have just had to rebuild my development computer and I can't compile ...
    (microsoft.public.pocketpc.developer)