MFC dead

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

um - 28 Apr 2005 21:52 GMT

What's the deadline for MFC ?

Reply to this Message

Carl Daniel [VC++ MVP] - 28 Apr 2005 23:30 GMT

> What's the deadline for MFC ?

For MFC to do what? MFC has significant additions in VC 2005 and will be
supported for the foreseeable future.

-cd

Reply to this Message

Ioannis Vranos - 28 Apr 2005 23:41 GMT

> For MFC to do what? MFC has significant additions in VC 2005 and will be
> supported for the foreseeable future.

Also as I have read on the web, an interesting thing from WinHEC which is currently
ongoing, is that Win32 will be updated too:

http://www.windowsitpro.com/windowspaulthurrott/Article/ArticleID/46166/windowsp
aulthurrott_46166.html
http://www.windowsitpro.com/windowspaulthurrott/Article/ArticleID/46175/windowsp
aulthurrott_46175.html

Win32 is mentioned in the second.

Reply to this Message

Ioannis Vranos - 28 Apr 2005 23:47 GMT

> Also as I have read on the web, an interesting thing from WinHEC which
> is currently ongoing, is that Win32 will be updated too:
>
> http://www.windowsitpro.com/windowspaulthurrott/Article/ArticleID/46166/windowsp
aulthurrott_46166.html
>
> http://www.windowsitpro.com/windowspaulthurrott/Article/ArticleID/46175/windowsp
aulthurrott_46175.html

Win32 is mentioned in the first.

And also:

http://www.windowsitpro.com/windowspaulthurrott/Article/ArticleID/46188/windowsp
aulthurrott_46188.html

Reply to this Message

Severian [MVP] - 29 Apr 2005 05:34 GMT

>MFC dead?

As far as I am concerned, it was dead the day it was released.

:)

--
Phillip Crews aka Severian
Microsoft MVP, Windows SDK
Posting email address is real, but please post replies on the newsgroup.

Reply to this Message

thatsalok - 29 Apr 2005 12:31 GMT

> *What's the deadline for MFC ? *

LOL! What the Joke!,MFC is backbone part of Visual C++

Reply to this Message

um - 29 Apr 2005 16:28 GMT

> > *What's the deadline for MFC ? *
>
> LOL! What the Joke!,MFC is backbone part of Visual C++

But in .NET it seems discouraged.

Reply to this Message

Carl Daniel [VC++ MVP] - 29 Apr 2005 16:49 GMT

>>> *What's the deadline for MFC ? *
>>
>> LOL! What the Joke!,MFC is backbone part of Visual C++
>
> But in .NET it seems discouraged.

.NET is not everything.

In fact, the major additions to MFC in VC 2005 are aimed at .NET <-> MFC
interoperability (for example, the ability to host a .NET form inside an MFC
view).

-cd

Reply to this Message

thatsalok - 30 Apr 2005 07:28 GMT

> > LOL! What the Joke!,MFC is backbone part of Visual C++
>
> But in .NET it seems discouraged. *

But! in VS 2005 it's get new life again

Reply to this Message

Ioannis Vranos - 30 Apr 2005 08:03 GMT

> But! in VS 2005 it's get new life again!

Personally, as far as I know, the main thing is .NET and the upcoming WinFX. Current
MFC/Win32 development is considered as "back-porting" to aid the development of current
applications. May be someone from MS can shed some light on it.

In any case, back-porting or not, people can do their job in Win32/MFC if they want to,
and having a number of choices is OK with me. :-)

Reply to this Message

thatsalok - 01 May 2005 12:26 GMT

> > But! in VS 2005 it's get new life again!
>
[quoted text clipped - 7 lines]
> Win32/MFC if they want to,
> and having a number of choices is OK with me. :-) *

Might be, But there Still MS don't want to Discourage MFC! (my Belief)

Reply to this Message

Ioannis Vranos - 01 May 2005 22:35 GMT

> Might be, But there Still MS don't want to Discourage MFC! (my Belief)

Well, as far as I know, the new API is WinFX. All the new stuff in Longhorn are developed
in this (for example the new communication API of Windows, Indigo).

Current functionality is not written from scratch, but is being wrapped in .NET and WinFX
(as this is what makes sense). However new functionality is written from metal for WinFX.

Win32 API would remain in Windows for backwards compatibility (as is the case of Win16 today).

Now I have just read in that WinHEC report
(http://www.windowsitpro.com/windowspaulthurrott/Article/ArticleID/46166/windowsp
aulthurrott_46166.html)
that

"Some Longhorn features will be back-ported to Win32 (and not be made available only
through WinFX), which was unexpected. Very little was said about this, however."

Apart from the possibility of being some misconception/miscommunication in the show, I
take notice of the word "some", and I assume probably only the GUI stuff.

Reply to this Message

Severian [MVP] - 01 May 2005 13:00 GMT

>> But! in VS 2005 it's get new life again!
>
[quoted text clipped - 4 lines]
>In any case, back-porting or not, people can do their job in Win32/MFC if they want to,
>and having a number of choices is OK with me. :-)

I do almost everything using direct Win32; my biggest beef is that VC
help nearly always goes to .NET/ATL/MFC crap, so I have to use the
index. (Oh, and by the way, dynamic help is less than useless, and
"filtering" is simply broken.) I have yet to figure out some way to
get the API help I want, rather than the .NET/MFC/ATL help that VC is
determined to serve up when I hit F1.

.NET seems to be a CPU-hogging thing designed for the latest
generation of illiterate programmers and a big boon for processor
manufacturers (a layer on a layer on a layer). I prefer to work a
little closer to the metal. I like to understand what my code does,
rather than depend on some behind-the-curtain pretense.

Perhaps that's natural for me, as a former VAX/VMS and Un*x systems
programmer, but aren't people who work and code like me needed to keep
the software development world honest and the code reasonable?

Moniker? IUnknown? Things stuffed into classes or assemblies because
of some Directive from the Lizard of Oz? These are not improved design
and development, they are coercion and spin.

--
Phillip Crews aka Severian
Microsoft MVP, Windows SDK
Posting email address is real, but please post replies on the newsgroup.

Reply to this Message

Michael Viking - 02 May 2005 17:28 GMT

> I do almost everything using direct Win32; my biggest beef is that VC
> help nearly always goes to .NET/ATL/MFC crap, so I have to use the
> index. (Oh, and by the way, dynamic help is less than useless, and
> "filtering" is simply broken.) I have yet to figure out some way to
> get the API help I want, rather than the .NET/MFC/ATL help that VC is
> determined to serve up when I hit F1.

This might not work for you, it depends on what you don't mind missing, but
it works like a champ for me. Also, maybe it doesn't work with today's
latest, greatest HTML stuff; We still use VC6 so I wouldn't know. At any
rate, I always edit the MSDNxxx.Col file, which is just XML. I go through
and delete all the folders of stuff I don't want. After saving it, the next
time I open MSDN, it says "rebuilding index" or something like that and
after a time, it comes up without all the goo I have no interest in, and
thus it never matches the goo I don't want. Anyway, you might be able to
edit your .col file and remove the stuff you don't want.

> .NET seems to be a CPU-hogging thing designed for the latest
> generation of illiterate programmers and a big boon for processor
> manufacturers (a layer on a layer on a layer). I prefer to work a
> little closer to the metal. I like to understand what my code does,
> rather than depend on some behind-the-curtain pretense.

I agree completely!

-Michael Viking

Reply to this Message

Severian [MVP] - 02 May 2005 18:57 GMT

>> I do almost everything using direct Win32; my biggest beef is that VC
>> help nearly always goes to .NET/ATL/MFC crap, so I have to use the
[quoted text clipped - 12 lines]
>thus it never matches the goo I don't want. Anyway, you might be able to
>edit your .col file and remove the stuff you don't want.

Thank you very much! I will try this today. I have asked this question
several times on other newsgroups and never gotten a response. Perhaps
I needed to write a vitriolic post so more people would read it.!

>> .NET seems to be a CPU-hogging thing designed for the latest
>> generation of illiterate programmers and a big boon for processor
[quoted text clipped - 3 lines]
>
>I agree completely!

--
Phillip Crews aka Severian
Microsoft MVP, Windows SDK
Posting email address is real, but please post replies on the newsgroup.

Reply to this Message

Sean Cavanaugh - 02 May 2005 20:37 GMT

>>>LOL! What the Joke!,MFC is backbone part of Visual C++
>>
>>But in .NET it seems discouraged. *
>
> But! in VS 2005 it's get new life again!

We all know how using re-animator fluid turns out.

Reply to this Message

Jochen Kalmbach [MVP] - 11 Jun 2005 09:35 GMT

> What's the deadline for MFC ?

Just as an addition:

See: MFC: Visual Studio 2005 and Beyond
http://msdn.microsoft.com/visualc/whidbey/mfc2005/default.aspx