Moving from eVC++ 3.0 to Compact .NET framework

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
I have an application in eVC++ and I want to move to compact .NET framework.
I want to know the advantages of .NET framework over eVC++.
I also want to whether I should go for VB.NET or C# in the compact .NEt
framework.

How do VB.NET and C# compare?
 
From scratch, writing a small application for a client took about 4 weeks in
vc++. In VC#, the same sort of app took about three days.

C++ --> C# makes more sense.
 
If you already have the program done, there's little reason to port from
native code to managed code. The advantages of managed code are primarily:
a) the development environment is much more visual, allowing drag and drop
of controls, visual layout, etc., b) integration with SQL Server and SQL
Server CE is *very* good in managed code. If you're just looking for
something to do, look elsewhere. If you have to add remote or local
database support to your existing program, it might be worthwhile. If you
are going to redesign the UI of the application, then you will probably save
some time switching to managed code.

Paul T.
 
But which way should I go if I am planning to .NET compact framework. Should
I move to C#.NET as I already have a code in eVC++ or should I move to VB.NET.

How do C#.NET and VB.NET compare in capabilities? ( which is more powerful)

With which one of them I can reuse some of the older C++ code.
 
VB.Net and C# are similar in power. The main difference is that it's easier
to write untyped code in VB.Net (although it's usually not a good idea) and
in C# you can use pointers (although you seldom need to do so.) As a C++
developer myself, I chose C# since it is closer to C++ than VB.Net.

As for reusing old C++ code, as long as you keep it in C++ and expose
undecorated functions, you can call those functions from either C# or
VB.Net.

--
Ginny Caughey
..Net Compact Framework MVP
 
I agree with Ginny. Why change syntax? You already know C++. Most of C#
is C++ Lite (or at least C++ Slightly Different). You won't be able to
entirely keep your existing code, unless, as Ginny also mentioned, you make
it into a DLL and provide calls that C# code can make (you can't just copy
the contents of your C++ code into a C# file and have it work).

Paul T.
 
Back
Top