From f05ebca6c9d20fa0f125cb623e3059021bca9e53 Mon Sep 17 00:00:00 2001 From: mjjo Date: Sat, 20 Jul 2013 23:25:45 +0000 Subject: [PATCH] --- CheckServer/ReadMe.txt | 105 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 105 insertions(+) create mode 100644 CheckServer/ReadMe.txt diff --git a/CheckServer/ReadMe.txt b/CheckServer/ReadMe.txt new file mode 100644 index 0000000..8784faa --- /dev/null +++ b/CheckServer/ReadMe.txt @@ -0,0 +1,105 @@ +======================================================================== + MICROSOFT FOUNDATION CLASS LIBRARY : CheckServer +======================================================================== + + +AppWizard has created this CheckServer 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 CheckServer application. + +CheckServer.dsp + This file (the project file) contains information at the project level and + is used to build a single project or subproject. Other users can share the + project (.dsp) file, but they should export the makefiles locally. + +CheckServer.h + This is the main header file for the application. It includes other + project specific headers (including Resource.h) and declares the + CCheckServerApp application class. + +CheckServer.cpp + This is the main application source file that contains the application + class CCheckServerApp. + +CheckServer.rc + 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++. + +CheckServer.clw + This file contains information used by ClassWizard to edit existing + classes or add new classes. ClassWizard also uses this file to store + information needed to create and edit message maps and dialog data + maps and to create prototype member functions. + +res\CheckServer.ico + This is an icon file, which is used as the application's icon. This + icon is included by the main resource file CheckServer.rc. + +res\CheckServer.rc2 + 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. + + + +///////////////////////////////////////////////////////////////////////////// + +For the main frame window: + +MainFrm.h, MainFrm.cpp + These files contain the frame class CMainFrame, which is derived from + CFrameWnd and controls all SDI frame features. + +res\Toolbar.bmp + This bitmap file is used to create tiled images for the toolbar. + The initial toolbar and status bar are constructed in the CMainFrame + class. Edit this toolbar bitmap using the resource editor, and + update the IDR_MAINFRAME TOOLBAR array in CheckServer.rc to add + toolbar buttons. +///////////////////////////////////////////////////////////////////////////// + +AppWizard creates one document type and one view: + +CheckServerDoc.h, CheckServerDoc.cpp - the document + These files contain your CCheckServerDoc class. Edit these files to + add your special document data and to implement file saving and loading + (via CCheckServerDoc::Serialize). + +CheckServerView.h, CheckServerView.cpp - the view of the document + These files contain your CCheckServerView class. + CCheckServerView objects are used to view CCheckServerDoc objects. + + + +///////////////////////////////////////////////////////////////////////////// +Other standard files: + +StdAfx.h, StdAfx.cpp + These files are used to build a precompiled header (PCH) file + named CheckServer.pch and a precompiled types file named StdAfx.obj. + +Resource.h + This is the standard header file, which defines new resource IDs. + Microsoft Visual C++ reads and updates this file. + +///////////////////////////////////////////////////////////////////////////// +Other notes: + +AppWizard 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 MFC42XXX.DLL +from the Microsoft Visual C++ CD-ROM onto the system or system32 directory, +and rename it to be MFCLOC.DLL. ("XXX" stands for the language abbreviation. +For example, MFC42DEU.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. + +/////////////////////////////////////////////////////////////////////////////