quote:1) If Windows Forms has a clear advantage over MFC, is it necessary or taking trouble learning MFC for a VC++ beginner?
MFC is an easy to use wrapper for Windows APIs. You learn MFC to do Windows Programming, programming for native windows environment, which involves Win 32 DLLs, COM development, application development etc.
Windows Forms, however is an abstraction of the things that you need to do to make a Windows application with various forms. I call it an abstraction 'cause the whole thing is designed to be portable, and thus has better affinity with .NET concepts. If Microsoft succeeds in developing Frameworks for other platforms, your application might as well run on platforms other than Windows without or with minimal changes in your application.
Actually if you are going with .NET and gonna stay with it, you donât need to learn either VC++ or MFC.
If, however, you are getting into core windows development you can hardly do anything substantial without learning VC++.
The two, as I mentioned earlier have different business areas.
quote:2) If Windows Forms still is in primitive/transitional stage, is it possible that MFC going to be phased out anyway, say in 2, or 3 years?
Now the question is not if Windows Forms will replace MFC, âcause the two have different business areas, but whether all windows programming will shift on .NET or not.
While it may seem like a possibility, I have my reservations about it, âcause .NET as I mentioned is designed to be portable, and even when more and more windows functionalities are being added to framework with its each new version, I believe core windows development would still be happening in VC++ and MFC will always be an integral part of it. So MFC is here to stay for at least those many years.
I would like to get comments on it if anybody sees longhorn bringing any drastic change in this equation.