MFC Migration

[gator]

I am thinking of migrating our MFC application to .NET using C++/CLI. My
question is does a migration from MFC applications and ATL to WinForms make
sense, given that XAML is likely to be the approach of the future?

[Tom Serface]

Hi Michael,

Microsoft has made no secret that trustworthy and secure computing is a huge
inititive of theirs (and should be ours). One of the components of that is
the managed code paradigm. However, like I said, they haven't really been
too pushy about it. Case in point, VS 2005 is even better at compiling
native code than was 2003. As time goes on and as .NET continues to improve
I think we'll all see the benefit of moving that direction. As we continue
down that path, we'll just keep getting our work done. :o)

Tom

"Michael Viking" <Th*******@swed en.se> wrote in message
news:eV******** ******@TK2MSFTN GP11.phx.gbl...

Well, I may be speaking out of turn and it's pretty hard to search for
articles of this nature to determine one way of the other. It's just the
general feeling I've developed over the years of reading these newsgroups.

-Michael Viking

[S7Solutions]

Read the whole thread of MFC/VC++ porting onto .Net and many many
companies are now helping clients port teh applications including us -
S7 [s7solutions.com] and is something almost every one is seeking
nowadays.

Regards
Manju

*** CUSTOMER comes FIRST, come what may ********

Manjunath M
S7 Software Solutions Pvt. Ltd.
#83 Railway Parallel Road, Kumara Park West
Bangalore - 560020, India
Telephone: [phone]
Fax: [phone]

2936 173rd CT NE
Redmond, WA 98052, USA
Telephone: [phone]
Fax: [phone]
Toll Free: 1-888-224-6174

Yahoo messenger ID: s7softwaresolut ions
MSN messenger ID: ma*******@hotma il.com
Skype ID: s7softwaresolut ions

http://www.s7solutions.com

"Redefining cross-platform porting & migration"

*************** *************** *************** ***

[David Ching]

"Marcus Heege" <NO****@heege.n et> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

Rewriting your code from scratch is not an option given that WPF is not
released and WinForms is not the API of the future.

Why are Winforms not the API of the future? Is everything going to be WPF?

Thanks,
David

[Tom Serface]

I'd put my money on WPF.

Tom

"David Ching" <[e-mail] > wrote in message
news:qD******** ***********@new ssvr13.news.pro digy.com...

"Marcus Heege" <NO****@heege.n et> wrote in message
news:%2******** ********@TK2MSF TNGP09.phx.gbl. ..

Rewriting your code from scratch is not an option given that WPF is not
released and WinForms is not the API of the future.

Why are Winforms not the API of the future? Is everything going to be
WPF?

Thanks,
David

[John C]

gator wrote:

*I am thinking of migrating our MFC application to .NET using
C++/CLI. My
question is does a migration from MFC applications and ATL to
WinForms make
sense, given that XAML is likely to be the approach of the future? *

XAML will be in mass use only by 2007 and I would suggest you to
migrate to Windows form first because that will help you for future
migration to XAML. I just finished my MFC application migration to C#
and it was not as difficult as I thought because writing code in .NET
is compact and really faster. I used RC Converter (
http://www.dudelabs.com ) to convert UI from MFC to Windows
Form. RC Converter supports VB.NET and C++/CLI too so for your C++/CLI
project it should not be a problem.After UI I wrote all business logic
code from scratch and it did not take that long. I would suggest you to
migrate to windows form first.

--
John C
------------------------------------------------------------------------
Posted via http://www.codecomments.com
------------------------------------------------------------------------