source: abuse/tags/win32/AbuseInstaller/ReadMe.txt @ 475

Last change on this file since 475 was 100, checked in by Sam Hocevar, 15 years ago
  • Importing an old Win32 port by Jeremy "Marauder" Scott.
  • Property svn:keywords set to Id
File size: 3.6 KB
Line 
1========================================================================
2       MICROSOFT FOUNDATION CLASS LIBRARY : AbuseInstaller
3========================================================================
4
5
6AppWizard has created this AbuseInstaller application for you.  This application
7not only demonstrates the basics of using the Microsoft Foundation classes
8but is also a starting point for writing your application.
9
10This file contains a summary of what you will find in each of the files that
11make up your AbuseInstaller application.
12
13AbuseInstaller.dsp
14    This file (the project file) contains information at the project level and
15    is used to build a single project or subproject. Other users can share the
16    project (.dsp) file, but they should export the makefiles locally.
17
18AbuseInstaller.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    CAbuseInstallerApp application class.
22
23AbuseInstaller.cpp
24    This is the main application source file that contains the application
25    class CAbuseInstallerApp.
26
27AbuseInstaller.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++.
32
33AbuseInstaller.clw
34    This file contains information used by ClassWizard to edit existing
35    classes or add new classes.  ClassWizard also uses this file to store
36    information needed to create and edit message maps and dialog data
37    maps and to create prototype member functions.
38
39res\AbuseInstaller.ico
40    This is an icon file, which is used as the application's icon.  This
41    icon is included by the main resource file AbuseInstaller.rc.
42
43res\AbuseInstaller.rc2
44    This file contains resources that are not edited by Microsoft
45        Visual C++.  You should place all resources not editable by
46        the resource editor in this file.
47
48
49
50
51/////////////////////////////////////////////////////////////////////////////
52
53AppWizard creates one dialog class:
54
55AbuseInstallerDlg.h, AbuseInstallerDlg.cpp - the dialog
56    These files contain your CAbuseInstallerDlg class.  This class defines
57    the behavior of your application's main dialog.  The dialog's
58    template is in AbuseInstaller.rc, which can be edited in Microsoft
59        Visual C++.
60
61
62/////////////////////////////////////////////////////////////////////////////
63Other standard files:
64
65StdAfx.h, StdAfx.cpp
66    These files are used to build a precompiled header (PCH) file
67    named AbuseInstaller.pch and a precompiled types file named StdAfx.obj.
68
69Resource.h
70    This is the standard header file, which defines new resource IDs.
71    Microsoft Visual C++ reads and updates this file.
72
73/////////////////////////////////////////////////////////////////////////////
74Other notes:
75
76AppWizard uses "TODO:" to indicate parts of the source code you
77should add to or customize.
78
79If your application uses MFC in a shared DLL, and your application is
80in a language other than the operating system's current language, you
81will need to copy the corresponding localized resources MFC42XXX.DLL
82from the Microsoft Visual C++ CD-ROM onto the system or system32 directory,
83and rename it to be MFCLOC.DLL.  ("XXX" stands for the language abbreviation.
84For example, MFC42DEU.DLL contains resources translated to German.)  If you
85don't do this, some of the UI elements of your application will remain in the
86language of the operating system.
87
88/////////////////////////////////////////////////////////////////////////////
Note: See TracBrowser for help on using the repository browser.