This article needs references that appear in reliable third-party publications. Primary sources or sources affiliated with the subject are generally not sufficient for a Wikipedia article. Please add more appropriate citations from reliable sources. (September 2009)

Microsoft Foundation Class Library

Developer(s)	Microsoft
Initial release	1992
Stable release	9.0.30411 [1] [2] / April 22, 2008 (RTW) [1] [2]
Written in	C++
Operating system	Microsoft Windows
Type	Development library
License	Proprietary
Website	MFC reference, 2008 Feature Pack reference

The Microsoft Foundation Class Library (also Microsoft Foundation Classes or MFC) is a library that wraps portions of the Windows API in C++ classes, including functionality that enables them to use a default application framework. Classes are defined for many of the handle-managed Windows objects and also for predefined windows and common controls.

Contents 1 History 2 Features 3 Visual C++ 2008 Feature Pack 4 Versions 5 Other application frameworks 6 References 7 Further reading 8 External links

[edit] History

MFC was introduced in 1992 with Microsoft's C/C++ 7.0 compiler for use with 16-bit versions of Windows as an extremely thin object-oriented C++ wrapper for the Windows API. C++ was just beginning to replace C for development of commercial application software as the predominant way to interface to the API. With that, they also shipped the very first replacement for an older, alphanumeric IDE called PWB.

One interesting quirk of MFC is the use of "Afx" as the prefix for many functions, macros and the standard precompiled header name "stdafx.h". During early development what became MFC was called "Application Framework Extensions" and abbreviated "Afx". The name Microsoft Foundation Classes (MFC) was adopted too late in the release cycle to change these references.

MFC 8.0 was released with Visual Studio 2005. MFC 9.0 was released with Visual Studio 2008. MFC is not included in the free edition of Visual C++ 2005/2008 Express.^[3]

The Object Windows Library (OWL), designed for use with Borland's Turbo C++ compiler, was a competing product introduced by Borland around the same time. Eventually, Borland discontinued OWL development and licensed the distribution of the MFC headers, libraries and DLLs from Microsoft^[4] for a short time, though it never offered fully integrated support for MFC. Borland later released VCL (Visual Component Library) to replace the OWL framework.

Microsoft's emphasis on MFC has been reduced in favor of their .NET Framework. MFC 7, 8 and 9 bridge elements of MFC with the .NET Framework to aid developers in migrating to the new framework. The MSVC++ compiler backend can emit managed and native object file(s). The linker can then build them together, generating hybrid (both managed and native) applications, allowing existing native applications to use managed extensions in a seamless manner. Though Microsoft has de-emphasized MFC, it remains a popular and widely used framework.

A lightweight alternative to MFC is the Windows Template Library (WTL). The free Visual C++ Express version compiles WTL applications, but does not include the IDE support of the Standard, Professional and Team editions. In an MFC program, direct Windows API calls are rarely needed. Instead, programs create objects from MFC classes and call member functions belonging to those objects. Many of those functions share their names with corresponding API functions.^[5]

[edit] Features

When MFC was introduced, it provided C++ macros for Windows message-handling (via Message Maps), exceptions, run-time type identification (RTTI), serialization and dynamic class instantiation. The macros for message-handling were intended to reduce memory consumption by avoiding gratuitous virtual table use and also provide a more concrete structure for various Visual C++-supplied tools to edit and manipulate code without parsing the full language. The message-handling macros replaced the virtual function mechanism provided by C++.

The macros for serialization, exceptions, and RTTI predated availability of these features in Microsoft C++ by a number of years. 32-bit versions of MFC, for Windows NT 3.1 and later Windows operating systems, used compilers that implemented the language features and updated the macros to simply wrap the language features instead of providing customized implementations, realizing upward compatibility.

[edit] Visual C++ 2008 Feature Pack

On April 7, 2008, Microsoft released an update to the MFC classes as an out-of-band update to Visual Studio 2008 and MFC 9.^[6] The update features new user interface constructs, including the Ribbon user interface of Microsoft Office 2007 and associated UI widgets, fully customizable toolbars, docking panes like Visual Studio 2005 (which can either be freely floated or docked to any side) and document tabs.^[7] However, the Ribbon elements needs to be created in code; it does not support the XML-based declarative markup like the RibbonX API in Microsoft Office 2007. The MFC application wizard has also been upgraded to support the new features – including a check-box to select whether the application will use the Ribbon or the Visual Studio 2005 user interface elements. The new functionality is provided in new classes so that old applications still continue to run.^[7] This update is building on top of BCGSoft’s BCGControlBar Library Professional Edition.^[8]

Microsoft has also imposed additional licensing requirements on users of the Ribbon UI.^[9] These include a requirement to adhere to Microsoft UI Design Guidelines, and a prohibition against using such a UI in applications which compete with Microsoft applications.

[edit] Versions

Product version	MFC version	Year introduced
Microsoft C/C++ 7.0	MFC 1.0	1993
Visual C++ 1.0	MFC 2.0
Visual C++ 1.5	MFC 2.5
Visual C++ 1.52c	MFC 2.5 (Last development platform for Windows 3.x)
Visual C++ 2.0	MFC 3.0
Visual C++ 2.1	MFC 3.1
Visual C++ 2.2	MFC 3.2
Visual C++ 4.0	MFC 4.0 (mfc40.dll included with Windows 95)	Aug 1995
Visual C++ 4.1	MFC 4.1
Visual C++ 4.2	MFC 4.2 (mfc42.dll included with the Windows 98 original release)	Mar 1998
eMbedded Visual C++ 3.0	MFC 4.2 (mfc42.dll)
Visual C++ 5.0	MFC 4.21 (mfc42.dll), a major upgrade from MFC 4.2.
Visual C++ 6.0	MFC 6.0 (mfc42.dll)	1998
eMbedded Visual C++ 4.0
Visual C++ .NET 2002 (Visual C++ 7.0)	MFC 7.0 (mfc70.dll), .NET 1.0	Feb 2002
Visual C++ .NET 2003 (Visual C++ 7.1)	MFC 7.1 (mfc71.dll), .NET 1.1	Apr 2003
Visual C++ 20051 (Visual C++ 8.0)	MFC 8.0 (mfc80.dll), .NET 2.0	Oct 2005
Visual C++ 20081 (Visual C++ 9.0)	MFC 9.0.21022 (mfc90.dll), .NET 3.5	Nov 2007
Visual C++ 2008 with Feature Pack	MFC 9.0.30411 (mfc90.dll)	Apr 2008
Visual C++ 2008 SP1	MFC 9.0.30729 (mfc90.dll)	Aug 2008
Visual C++ 2010	MFC 10.x(?), .NET 4.0	Est. 2010

• ¹ The Visual Studio Express Editions do not include the MFC libraries.

[edit] Other application frameworks

• Object Windows Library
• MacApp
• PowerPlant (Mac OS X)
• Visual Component Library
• Active Template Library (ATL)
• Windows Template Library (WTL)
• .NET Framework
• Win32++ – C++ library used to build windows applications
• Cocoa (Mac OS X, Objective C)
• Fox toolkit (multi-platform)
• wxWidgets (multi-platform, formerly wxWindows)
• Qt (toolkit) (multi-platform)
• GTK+ (multi-platform)
• SmartWin++

[edit] References

[edit] Further reading

• Shepherd, George (1996). MFC Internals. Addison-Wesley. ISBN 0-201-40721-3. 
• Kruglinski, David (1996). Inside Visual C++. Microsoft Press. ISBN 0-55615-891-2. 
• Microsoft Corporation (1995). Microsoft Visual C++ Programming with MFC. Microsoft Press. ISBN 1-55615-921-8. 

[edit] External links

• MSDN MFC Reference
• MSDN MFC newsgroup
• MFC: Visual Studio 2005 and Beyond
• An Inside Look At The Next Generation Of Visual C++ (covers the major MFC 9 updates)