mfc to .net

  • Thread starter Thread starter dotnetchic
  • Start date Start date
D

dotnetchic

I am about to develop a plan for porting our codebase from vc++/MFC to
vs 2005 -- eventually, we would like to end up with the majority of the
codebase in c#. But I guess initially we'll be moving to c++/clr
(using :oldSyntax?).

Just looking for advice/comments/reference material and whether anyone
has some experience I might leverage.

TIA,
Sharon
 
managed c++ is different enough that you are essentially re-writing the app.
Not to mention that the MFC thing goes out the door as well. When you look
at the big picture, you are re-writing so you should re-write in c#.

--

________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Professional VSTO.NET - Wrox/Wiley 2006
 
Is that the case? I've read several articles to the contrary recently
(I believe the most recent was on Code Project). I know there's the
issue of conversion to windows forms so all the dialogs/forms/property
pages must be converted. And then there are some type-safety and
variable scope issues to deal with, but that's hardly a rewrite.

Am I missing something?

Regards,
Sharon
 
Apologies, in my OP I stated we would move to c++/clr what I meant was
c++/cli, the common language infrastructure which I've heard is
better/nicer/easier than managed c++. I should probably have
cross-posted this to c++ group, but I was looking for advice from the
c# world instead :)

Regards,
-Sharon
 
For our project we used a product called RC Converter (dudelabs.com).
It will convert the dialogs, views, etc to Windows Forms in C++/CLI or
C#. The business logic we converted to c++/clr with some tweaking.
 
you'd convert a real world app to another language using a tool or otherwise
and not verify the code line by line, in addition to not re-testing
everything from scratch, not too mention the various optimizations that you
necessarily have to implement since tools are notably inefficient at this?
If you wouldn't do that, then that effort is equivalent to a rewrite IMO. If
you would trust the tool and package and ship the product then I guess
that's fine for you - not for me though.

--

________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Professional VSTO.NET - Wrox/Wiley 2006
 
I'm not talking about shipping a product, I'm talking about a process
for conversion. If there's a workable intermediate that I can produce
before we take on the C# conversion, then my managers will see the
bottom line as results. And that's really all they care about. What I
care about it chunking MFC and converting C#. Just a means to an end.
 
Yes, I downloaded a trial of the RC Converter, but it will only convert
a single file at a time or something. From what I remember it was
relatively inexpensive...were you happy with the results? Can you
estimate the time it took to convert business logic on a class/module
basis?

Thanks,
Sharon
 
Back
Top