MICROSOFT FOUNDATION CLASS LIBRARY : BinaryTreeDemo Project Overview
The application wizard has created this BinaryTreeDemo application for
you. This application not only demonstrates the basics of using the Microsoft
Foundation Classes but is also a starting point for writing your application.
This file contains a summary of what you will find in each of the files that
make up your BinaryTreeDemo application.
This is the main project file for VC++ projects generated using an application wizard.
It contains information about the version of Visual C++ that generated the file, and
information about the platforms, configurations, and project features selected with the
This is the main header file for the application. It includes other
project specific headers (including Resource.h) and declares the
CBinaryTreeDemoApp application class.
This is the main application source file that contains the application
This is a listing of all of the Microsoft Windows resources that the
program uses. It includes the icons, bitmaps, and cursors that are stored
in the RES subdirectory. This file can be directly edited in Microsoft
Visual C++. Your project resources are in 1033.
This is an icon file, which is used as the application's icon. This
icon is included by the main resource file BinaryTreeDemo.rc.
This file contains resources that are not edited by Microsoft
Visual C++. You should place all resources not editable by
the resource editor in this file.
The application wizard creates one dialog class:
BinaryTreeDemoDlg.h, BinaryTreeDemoDlg.cpp - the dialog
These files contain your CBinaryTreeDemoDlg class. This class defines
the behavior of your application's main dialog. The dialog's template is
in BinaryTreeDemo.rc, which can be edited in Microsoft Visual C++.
Other standard files:
These files are used to build a precompiled header (PCH) file
named BinaryTreeDemo.pch and a precompiled types file named StdAfx.obj.
This is the standard header file, which defines new resource IDs.
Microsoft Visual C++ reads and updates this file.
Application manifest files are used by Windows XP to describe an applications
dependency on specific versions of Side-by-Side assemblies. The loader uses this
information to load the appropriate assembly from the assembly cache or private
from the application. The Application manifest maybe included for redistribution
as an external .manifest file that is installed in the same folder as the application
executable or it may be included in the executable in the form of a resource.
The application wizard uses "TODO:" to indicate parts of the source code you
should add to or customize.
If your application uses MFC in a shared DLL, and your application is in a
language other than the operating system's current language, you will need
to copy the corresponding localized resources MFC70XXX.DLL from the Microsoft
Visual C++ CD-ROM under the Win\System directory to your computer's system or
system32 directory, and rename it to be MFCLOC.DLL. ("XXX" stands for the
language abbreviation. For example, MFC70DEU.DLL contains resources
translated to German.) If you don't do this, some of the UI elements of
your application will remain in the language of the operating system.
By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.
If a file you wish to view isn't highlighted, and is a text file (not binary), please
let us know and we'll add colourisation support for it.