Re: How about the future of VC++/MFC
- From: Joseph M. Newcomer <newcomer@xxxxxxxxxxxx>
- Date: Mon, 27 Nov 2006 22:36:04 -0500
The problem is not discussing whether or not MFC is dead, but whether or not new
initiatives require learning .NET. As far as I can tell, there is little technical excuse
for NOT learning NET technology; I work on it as time permits. Excuses of lack of time
are, alas, all too prevalent (and is the reason I don't know more about .NET). But that
wasn't the question. The question was whether MFC is dead.
The future of MFC is not the same question as the future of .NET, and the two questions
should not be confused.
I find the lack of doc/view in C# is a real pain. The lack of STRINGTABLE, MESSAGETABLE,
and dialog template resources seems insane. But the ToString concept (and reflection in
general) is powerful. I haven't looked at the new C# but it appears to fix a number of
serious defects of the first release (particularly generics). So I learn it as I can,
because someday some customer is going to come to me with a .NET need and I'd better be
prepared enough to not make a complete fool of myself.
joe
On 27 Nov 2006 18:59:03 -0800, "Ajay Kalra" <ajaykalra@xxxxxxxxx> wrote:
Joseph M. Newcomer [MVP]
And, the kicker is, you need to use C# to create XAML UI's. Not even
C++/CLI will create XAML apps because it doesn't support partial classes.
This really sucks and basically relegates C++/CLI back to being a
second-class .NET citizen just like when VC++ didn't come with a WinForms
designer. But XAML requires .NET. This is the must-have reason for
learning .NET now.
MSFT sent a clear signal several years ago that .Net is the preferred
platform for all development. IMO, C++ is now a second class
language/plaform wrt .Net and the languages it supports. All major
initiatives are going to be .Net based. MFC is not going to die but the
direction of the market(forced by MSFT) is clearly .Net.
---
Ajay
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.
- Follow-Ups:
- Re: How about the future of VC++/MFC
- From: Mihai N.
- Re: How about the future of VC++/MFC
- References:
- How about the future of VC++/MFC
- From: workaholic
- Re: How about the future of VC++/MFC
- From: Joseph M . Newcomer
- Re: How about the future of VC++/MFC
- From: David Webber
- Re: How about the future of VC++/MFC
- From: Joseph M . Newcomer
- Re: How about the future of VC++/MFC
- From: David Ching
- Re: How about the future of VC++/MFC
- From: Ajay Kalra
- How about the future of VC++/MFC
- Prev by Date: Re: WideChartoMultiByte problems
- Next by Date: wrapper class doubt
- Previous by thread: Re: How about the future of VC++/MFC
- Next by thread: Re: How about the future of VC++/MFC
- Index(es):
Relevant Pages
|
Loading