How to port eVC4 project to VS2003

  • Thread starter Thread starter KDelta
  • Start date Start date
K

KDelta

Hello,

I have several eVC4 projects that I would like to convert to Visual Studio
2003 .Net.

Is this possible through some sort of Wizard?

If I create a VS project/solution can I add the evc4 files and compile
them?

Thanks,
AD

remove - from address to reply
 
eVC4 allows you to target CE devices with unmanaged/native code (C++) only

VS2003.NET allows you to target CE devices with managed code (C# or VB) only

So there is little point in trying the conversion.

I doubt what you are really after is to convert the C++ projects so you can
run them on the desktop (VS2003 supports C++ for the PC) since there is
little point in that.

As an aside, VS2005 will allow you to write C++ for devices, but still not
managed C++.

Cheers
Daniel
 
Thanks for the info.

To clarify, I want to build CE apps in Visual Studio using unmanaged C++
by porting my "old" eVC4 projects to VSNet.

From your reply it looks like I need VS2005 to use C++ for CE.
 
From your reply it looks like I need VS2005 to use C++ for CE.
You've got it (or stick with your existing eVC projects).

There is a development matrix here for PPC and SP:
http://blogs.msdn.com/windowsmobile/archive/2004/09/22/233071.aspx

And in the comments of this blog entry (last June) the statement is
" 1. For VS 2005, in Beta 1 we are supporting Windows CE 5.0 as well as
Windows Mobile 2003. For the final release the list of supported Versions is
being finalized. "
http://blogs.msdn.com/amit_chopra/archive/2004/03/10/87386.aspx

I cannot locate an official statement of whether VS2005 will allow native
development for pre-CE 5.0 devices (we know managed code is only CE 5.0
onwards). If anybody has public knowledge of the opposite feel free to jump
in.

Cheers
Daniel
 
I would stick with eVC 4 for pre-5.0 devices for now. What is the reason
for this porting effort? What are you (KDelta), not getting from eVC 4 that
you think will be fixed by using VS.NET?

Paul T.
 
KDelta, to add to Paul's comments, I can now confirm that Whidbey will not
support pre-CE5.0 devices in native or managed code.

Cheers
Daniel
--
http://www.danielmoth.com/Blog/


Paul G. Tobey said:
I would stick with eVC 4 for pre-5.0 devices for now. What is the reason
for this porting effort? What are you (KDelta), not getting from eVC 4
that you think will be fixed by using VS.NET?

Paul T.
Click to expand...
 
Back
Top