| 1 |
================================================================================
|
| 2 |
MICROSOFT FOUNDATION CLASS LIBRARY : Client Project Overview
|
| 3 |
===============================================================================
|
| 4 |
|
| 5 |
The application wizard has created this Client application for
|
| 6 |
you. This application not only demonstrates the basics of using the Microsoft
|
| 7 |
Foundation Classes but is also a starting point for writing your application.
|
| 8 |
|
| 9 |
This file contains a summary of what you will find in each of the files that
|
| 10 |
make up your Client application.
|
| 11 |
|
| 12 |
Client.vcproj
|
| 13 |
This is the main project file for VC++ projects generated using an application wizard.
|
| 14 |
It contains information about the version of Visual C++ that generated the file, and
|
| 15 |
information about the platforms, configurations, and project features selected with the
|
| 16 |
application wizard.
|
| 17 |
|
| 18 |
Client.h
|
| 19 |
This is the main header file for the application. It includes other
|
| 20 |
project specific headers (including Resource.h) and declares the
|
| 21 |
CClientApp application class.
|
| 22 |
|
| 23 |
Client.cpp
|
| 24 |
This is the main application source file that contains the application
|
| 25 |
class CClientApp.
|
| 26 |
|
| 27 |
Client.rc
|
| 28 |
This is a listing of all of the Microsoft Windows resources that the
|
| 29 |
program uses. It includes the icons, bitmaps, and cursors that are stored
|
| 30 |
in the RES subdirectory. This file can be directly edited in Microsoft
|
| 31 |
Visual C++. Your project resources are in 1033.
|
| 32 |
|
| 33 |
res\Client.ico
|
| 34 |
This is an icon file, which is used as the application's icon. This
|
| 35 |
icon is included by the main resource file Client.rc.
|
| 36 |
|
| 37 |
res\Client.rc2
|
| 38 |
This file contains resources that are not edited by Microsoft
|
| 39 |
Visual C++. You should place all resources not editable by
|
| 40 |
the resource editor in this file.
|
| 41 |
|
| 42 |
/////////////////////////////////////////////////////////////////////////////
|
| 43 |
|
| 44 |
The application wizard creates one dialog class:
|
| 45 |
ClientDlg.h, ClientDlg.cpp - the dialog
|
| 46 |
These files contain your CClientDlg class. This class defines
|
| 47 |
the behavior of your application's main dialog. The dialog's template is
|
| 48 |
in Client.rc, which can be edited in Microsoft Visual C++.
|
| 49 |
/////////////////////////////////////////////////////////////////////////////
|
| 50 |
|
| 51 |
Other Features:
|
| 52 |
|
| 53 |
ActiveX Controls
|
| 54 |
The application includes support to use ActiveX controls.
|
| 55 |
|
| 56 |
Windows Sockets
|
| 57 |
The application has support for establishing communications over TCP/IP networks.
|
| 58 |
/////////////////////////////////////////////////////////////////////////////
|
| 59 |
|
| 60 |
Other standard files:
|
| 61 |
|
| 62 |
StdAfx.h, StdAfx.cpp
|
| 63 |
These files are used to build a precompiled header (PCH) file
|
| 64 |
named Client.pch and a precompiled types file named StdAfx.obj.
|
| 65 |
|
| 66 |
Resource.h
|
| 67 |
This is the standard header file, which defines new resource IDs.
|
| 68 |
Microsoft Visual C++ reads and updates this file.
|
| 69 |
|
| 70 |
Client.manifest
|
| 71 |
Application manifest files are used by Windows XP to describe an applications
|
| 72 |
dependency on specific versions of Side-by-Side assemblies. The loader uses this
|
| 73 |
information to load the appropriate assembly from the assembly cache or private
|
| 74 |
from the application. The Application manifest maybe included for redistribution
|
| 75 |
as an external .manifest file that is installed in the same folder as the application
|
| 76 |
executable or it may be included in the executable in the form of a resource.
|
| 77 |
/////////////////////////////////////////////////////////////////////////////
|
| 78 |
|
| 79 |
Other notes:
|
| 80 |
|
| 81 |
The application wizard uses "TODO:" to indicate parts of the source code you
|
| 82 |
should add to or customize.
|
| 83 |
|
| 84 |
If your application uses MFC in a shared DLL, and your application is in a
|
| 85 |
language other than the operating system's current language, you will need
|
| 86 |
to copy the corresponding localized resources MFC70XXX.DLL from the Microsoft
|
| 87 |
Visual C++ CD-ROM under the Win\System directory to your computer's system or
|
| 88 |
system32 directory, and rename it to be MFCLOC.DLL. ("XXX" stands for the
|
| 89 |
language abbreviation. For example, MFC70DEU.DLL contains resources
|
| 90 |
translated to German.) If you don't do this, some of the UI elements of
|
| 91 |
your application will remain in the language of the operating system.
|
| 92 |
|
| 93 |
/////////////////////////////////////////////////////////////////////////////
|
Parent Directory
| 
Revision Log