Hi Jim, MFC based GUIs are deprecated and have been superseded by the .NET framework. MFCs may have been the primary (if not sole) source of the term "dll hell." I did a count of MFC40 versions some years ago and the count was about fifteen or so. Just open up you Visual Studio and open a Windows application and set your widgets (buttons and other items) on the form. Double click and you have a handler automatically set up (unlike that annoying procedure in Visual Studio 6 and earlier). Other then this, you just program using classes and functions like any other C++ type program (C# nowadays).
Kevin --- In [email protected], "Jim McLaughlin" <wa2...@...> wrote: > > I have been working with CLR Console apps using Visual C++ 2008 Express. Now, > I too am looking to make the jump from the console to an event driven windows > GUI. Is MFC back in favor? Or is there a better approach? The IDE offers > Windows Forms Apps templates too. > > This thread has been very nformative but it is now 2009. What is the advice > today regarding Windows Forms or MFC? > > Many thanks! > > Jim > > > > Well, the reason MFC is a disaster in lieu of OO techniques is because we > > have to remember that it was developed as Visual C++ was developed. So, it > > has hacks and workarounds for compiler limitations built right into it. >
