Fabio said:
I have read that WinForms is not intended to be a replacement for
MFC; I've also read that .NET will replace all of the functionality
of MFC. Having not developed in MFC before, is it safe to go with
WinForms and ignore MFC, or will MFC still be able to do things that
WinForms can't in the future.
For the moment, there's no relationship between .Net and the MFC.
There's no MFC equivalent in the .Net environment today, even when
looking at third-party tools. MFC has the advantage of giving a base
structure to an application, enforcing a programming model,
Document/View, that is not as effective as the MVC model
(Model-View-Controller) but that is a good start. The MFC give you an UI
based on generally recognized standards, and raw functionality like
print preview, document management, view management, etc...
If the MFC do not produce amazingly well structured apps, at least they
provide a structure. WinForms don't. You won't find such functionality
in .Net at this time. The current .Net development tools are RAD
oriented (like VB6 or Delphi). So don't expect much support for MFC-like
functionality.
I'm one of those advocating for a .Net equivalent of the MFC. I think
that a "real" framework is missing in the current .Net development
tools. However, the .Net Architecture Center
(
http://msdn.microsoft.com/architecture/) provides sample .Net
implementation code of the MVC model that could be reused in our own
apps:
http://msdn.microsoft.com/architect...ull=/library/en-us/dnpatterns/html/DesMVC.asp .
Regards.
