Migrate to .NET

  • Thread starter Thread starter Tony Johansson
  • Start date Start date
T

Tony Johansson

Hello!

We have an MFC application written in VS6.0.

The application is badly written and designed so we assume to rewrite the
whole application using .NET.
We have a .NET Visual Studio 2003.
We will keep using C++.
Now to my question does it matter if we use the old VS2003 which we have or
use the new VS2005 when we will rewrite everything from scratch.

For example is it easier to use VS2005?

//Tony
 
Tony Johansson said:
Hello!

We have an MFC application written in VS6.0.

The application is badly written and designed so we assume to rewrite the
whole application using .NET.
We have a .NET Visual Studio 2003.
We will keep using C++.
Now to my question does it matter if we use the old VS2003 which we have
or use the new VS2005 when we will rewrite everything from scratch.

For example is it easier to use VS2005?

//Tony
Click to expand...
Assuming that by "...to rewrite the whole application using .NET" you mean
that you intend to use .NET Framework classes instead of MFC, I'd recommend
Visual Studio 2005, as a lot of work has been done to enhance the way
managed C++ works with the Framework. Either way, you're going to encounter
a learning curve, so you should take advantage of the new features.
Just my opinion.
 
Note that when it comes to converting your code, 2003 and 2005 are NOT the
same. 2003 and 2005 are somewhat incompatible with each other. Hence you
need to decide which one you want to convert to and stick to it.

That being said, it looks like converting 2003 code to 2005 code won't be
too difficult, but I haven't done it yet (still waiting for 2005 to arrive
as part of my company's MSDN subscription). See here for how to do it:

http://msdn2.microsoft.com/en-us/library/b23b94s7.aspx

[==P==]
 
Back
Top