Re: EVC3, EVC4 or VStudio 2005?

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

Well, I was not looking for support or fixes, since I applied a working fix
myself :-)

I was merely providing the original poster some additional input to
consider, with which he could make a decision regarding his question, which
was: "Should I convert the two program to VS2005".
My goal was to point out that such a conversion might not be entirely
troublefree; my goal was not to get any support, since the cause of the
problem was obvious and the solution is simple (even though you may not
agree with it).

The other people experiencing the same problem are people within our company
trying to build the same product. They came to me reporting the same errors
and how they fixed it. This was by manually adapting the SDK headers, or by
copying the WM5 headers, as I had done.

Since it was the same product they are building, it is still possible that
the problem is in some setting or compiler flag, as I said before. But I
don't think it is anything in my environment; in that case it would be just
me having the problem.

How you could be more constructive? Look at the 'vector' example and see if
you can think of something that would make it compile without the 'typename'
error. That could then give me a clue as to where I went wrong, if indeed it
is a mistake I made.
But don't repeat that it works for you, I got that :-) and its not
constructive.

Etienne

"<ctacke/>" <ctacke[@]opennetcf[dot]com> schreef in bericht
news:%23A6o22JPHHA.1240@xxxxxxxxxxxxxxxxxxxxxxx
How could I be more constructive? I'm saying that I have the same SDK and
that it works. I'm saying I made no changes to my environment. I'd be
happy to offer suggestion of what is wrong with yours, but I've never seen
the error, nor seen it reported (and I've been reading this newsgroup
daily for probably 6 years). You say that you're not the only one
experiencing this - who are the others? What did they do to resolve it?

I do know that mucking with the SDK to try to get it to build is the wrong
way to attempt to fix it. The right fix is to open a support case with
Microsoft. Maybe something about your environment found a bug in the
installer, maybe the planets aligned in just a way that the compiler is
doing something not right. Microsoft would be interested to know what
happened so they can come up with a resolution for both you and any others
with the problem. In fact these are the things that often become KB
articles.

Bear in mind that while MS employees often read these groups, these
newsgroups are not an official support channel. No case numer is assigned
and no one is accountable for resolving anything posted here. If you want
it fixed call them. Get a case number. I guarantee is will get resolved
that way.


--
Chris Tacke
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
--



"ET" <e.thijsse@xxxxxxxxx> wrote in message
news:9b912$45b20f20$5962efda$7874@xxxxxxxxxxxxxxxxx
Then I can only assume you are not using these six header files that I
had trouble with....

But this kind of response is not very helpful.
Instead of continuing to express your disbelief, maybe you could respond
in a more constructive manner, for example, maybe you have an idea as to
what could be wrong in my environment...

Or maybe you have an idea why the missing 'typename' keyword does not
produce an error in your environment... That would be a lot more helpful.

For the record, I am also using VS2005 right out of the box, and I am not
the only one experiencing the problem.

Thanks,

Etienne

"<ctacke/>" <ctacke[@]opennetcf[dot]com> schreef in bericht
news:uaZv9CCPHHA.2468@xxxxxxxxxxxxxxxxxxxxxxx
And I'm saying I'm using Studio 2005, just as it came out of the box,
and I see no errors or warnings when targeting PPC 2003 or WM devices.
I know many other people that are doing the same. I can therefore only
conclude that something is wrong with your environment.


--
Chris Tacke
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
--




"ET" <e.thijsse@xxxxxxxxx> wrote in message
news:ce677$45b1454c$5962efda$7828@xxxxxxxxxxxxxxxxx
I will give an example:

In the PocketPC2003 SDK that is in VS2005 there is a C++ header file
called "vector".
In this header, there are the following lines:

typedef _A::size_type size_type;
typedef _A::difference_type difference_type;
typedef _A::pointer _Tptr;
typedef _A::const_pointer _Ctptr;
typedef _A::reference reference;
typedef _A::const_reference const_reference;
typedef _A::value_type value_type;

VS2005 C++ compiler complains about these lines, saying that 'typename'
must be inserted.

Looking at the WM5 SDK, in the same header file "vector", this file is
almost identical to the PocketPC2003 one, except for these particular
lines, which read:

typedef typename _A::size_type size_type;
typedef typename _A::difference_type difference_type;
typedef typename _A::pointer _Tptr;
typedef typename _A::const_pointer _Ctptr;
typedef typename _A::reference reference;
typedef typename _A::const_reference const_reference;
typedef typename _A::value_type value_type;

Therefore, I copied the WM5 version into the PocketPC2003 SDK, and
voila, no more complaints from the compiler about this header.

As you can see, the errors are easy to fix, but I still think the SDK
delivered with VS2005 should have had this fixed...

Thanks,

Etienne

"<ctacke/>" <ctacke[@]opennetcf[dot]com> schreef in bericht
news:uIYox5APHHA.4332@xxxxxxxxxxxxxxxxxxxxxxx
Yes, my point is I was using Studio 2005 when it was a Beta and have
been using it ever since and I've never had a problem. So I've got
probably 2 years of usage without seeing what you're reporting. I
also know several other developers with the same experience as me.
I've not made any settings changes - I'm using it as installed, right
out of the box.


--
Chris Tacke
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
--




"ET" <e.thijsse@xxxxxxxxx> wrote in message
news:c4112$45b1320d$5962efda$23680@xxxxxxxxxxxxxxxxx
True, before VS2005, there was no problem...
The problem is with VS2005, not with anything before that; VS .NET
worked fine, eVC4 worked fine.
Just not VS2005...

Did you use VS2005 ? Maybe there is a setting somewhere with which
you can turn off these new language features; I don't know; I didn't
find it.

Etienne

"<ctacke/>" <ctacke[@]opennetcf[dot]com> schreef in bericht
news:OiF5im2OHHA.4644@xxxxxxxxxxxxxxxxxxxxxxx
I find that hard to believe. There's got to be something wrong with
what you've got set up. I've been developing since before Studio '05
was released using the PPC 03 SDK (I rarely use the WM SDK) and I've
seen no problems at all.


--
Chris Tacke
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
--




"ET" <e.thijsse@xxxxxxxxx> wrote in message
news:618f9$45affc09$5962efda$1343@xxxxxxxxxxxxxxxxx
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: EVC3, EVC4 or VStudio 2005?
    ... older SDK. ... that the problem is in some setting or compiler flag, ... 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 ...
    (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?
    ... Then I can only assume you are not using these six header files that I had ... VS2005 C++ compiler complains about these lines, ... Looking at the WM5 SDK, in the same header file "vector", this file is ... Therefore, I copied the WM5 version into the PocketPC2003 SDK, and voila, ...
    (microsoft.public.pocketpc.developer)
  • Re: EVC3, EVC4 or VStudio 2005?
    ... VS2005 C++ compiler complains about these lines, ... Looking at the WM5 SDK, in the same header file "vector", this file is ... Therefore, I copied the WM5 version into the PocketPC2003 SDK, and voila, ...
    (microsoft.public.pocketpc.developer)
  • Re: EVC3, EVC4 or VStudio 2005?
    ... In the PocketPC2003 SDK that is in VS2005 there is a C++ header file called ... VS2005 C++ compiler complains about these lines, ... Therefore, I copied the WM5 version into the PocketPC2003 SDK, and voila, no ...
    (microsoft.public.pocketpc.developer)