From: unf on
Could anybody tell me what is the future of MFC? I never used that library.
I just got some skills in pure C++. But some knowledgeable people are saying
it's not a good idea to study MFC, because "it's going to be obsolete" and
replaced by .Net. They advise me to study C# because as they say "studying
MFC will take you quite a lot of time by which Longhorn will be released and
all coding will be done in managed way"... Well, I really don't know which
direction to elect

From: thatsalok on
According to me :)
MFC never be obsolete and it would be safe bet to
study MFC in current scenario

--

With Regards
Alok Gupta
Visit me at http://alok.bizhat.com

"I Believe this will Help"

"unf" <unf(a)discussions.microsoft.com> wrote in message
news:E4649F64-DDEF-4E53-AA55-71F88830D428(a)microsoft.com...
> Could anybody tell me what is the future of MFC? I never used that
library.
> I just got some skills in pure C++. But some knowledgeable people are
saying
> it's not a good idea to study MFC, because "it's going to be obsolete" and
> replaced by .Net. They advise me to study C# because as they say "studying
> MFC will take you quite a lot of time by which Longhorn will be released
and
> all coding will be done in managed way"... Well, I really don't know which
> direction to elect
>


From: Nishant Sivakumar on
Even if you want to do .NET development, there's always C++/CLI. So you
don't have to use less performant languages like C# or VB.NET. Google for
"C++/CLI" and you'll get tons of hits :-)

--
Regards,
Nish [VC++ MVP]
http://www.voidnish.com
http://blog.voidnish.com


"unf" <unf(a)discussions.microsoft.com> wrote in message
news:E4649F64-DDEF-4E53-AA55-71F88830D428(a)microsoft.com...
> Could anybody tell me what is the future of MFC? I never used that
> library.
> I just got some skills in pure C++. But some knowledgeable people are
> saying
> it's not a good idea to study MFC, because "it's going to be obsolete" and
> replaced by .Net. They advise me to study C# because as they say "studying
> MFC will take you quite a lot of time by which Longhorn will be released
> and
> all coding will be done in managed way"... Well, I really don't know which
> direction to elect
>


From: Ajay Kalra on
> use less performant languages like C# or VB.NET

Hm...

>Google for "C++/CLI" and you'll get tons of hits

C++ CLI - 198K hits
C# 4.25 million hits
VB 12.6 million hits

------
Ajay Kalra
ajaykalra(a)yahoo.com

From: Jim Howard on
"unf" <unf(a)discussions.microsoft.com> wrote in message
news:E4649F64-DDEF-4E53-AA55-71F88830D428(a)microsoft.com...
> Could anybody tell me what is the future of MFC? I never used that
> library.
> I just got some skills in pure C++. <snip> "... Well, I really don't know
> which
> direction to elect
>

As long as Windows 98 computers exist in significant numbers MFC is one of
only two logical choices for developing client side "double clickable exe"
Windows applications for widespread deployment (the other choice is Delphi).
..Net is not an option for any application that: might need to be downloaded
over the internet and run on Win98 because of the huge size of the runtime
and low performance of .Net on older computers.

There are also thousands of legacy programs written using MFC that will need
maintenace for years to come, just as there is still lots of work for Cobol
programmers.

If you are interested in writing a ".exe" application that runs on as many
computers as possible then MFC is an entirely vivable option for that
purpose. Writing a significant application in MFC will certainly help you
understand how Windows actually works.

If you just want to find your first job then I don't know that learning MFC
would be worth the effort beyond playing with the wizards a bit to get a
feel for the libary. In that case I'd concentrate on learning how to write
both server side and and client side apps in both .Net and Java.