nthomas99 / testbencholrxapi

VC++ 2013 project to test OlrxAPI calls

================================================================================ Test Bench for OLRXAPI

This Visual Studio 2013 c++ application wizard project contains code to test OlrxAPI function calls.

This file contains a summary of what you will find in each of the files that make up the application.

/////////////////////////////////////////////////////////////////////////////

ASPEN OlrxAPI files

include\OlrxAPI.h Header file for OlrxAPI functions and constants definitions

bin\OlrxAPI.lib Object file library

///////////////////////////////////////////////////////////////////////////// VS 2013 application wizard generated files:

TestBenchOlrxAPI.vcxproj 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 application wizard.

TestBenchOlrxAPI.vcxproj.filters This is the filters file for VC++ projects generated using an Application Wizard. It contains information about the association between the files in your project and the filters. This association is used in the IDE to show grouping of files with similar extensions under a specific node (for e.g. ".cpp" files are associated with the "Source Files" filter).

TestBenchOlrxAPI.h This is the main header file for the application. It includes other project specific headers (including Resource.h) and declares the CUnittestApp application class.

TestBenchOlrxAPI.cpp This is the main application source file that contains the application class CUnittestApp.

Unittest.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++. Your project resources are in 1033.

res\Unittest.ico This is an icon file, which is used as the application's icon. This icon is included by the main resource file Unittest.rc.

res\Unittest.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.

/////////////////////////////////////////////////////////////////////////////

ASPEN OlrxAPI files

include\OlrxAPI.h Header file for OlrxAPI functions and constants definitions

bin\OlrxAPI.lib Object file library

/////////////////////////////////////////////////////////////////////////////

For the main frame window: The project includes a standard MFC interface.

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 Unittest.rc to add toolbar buttons. /////////////////////////////////////////////////////////////////////////////

The application wizard creates one document type and one view:

UnittestDoc.h, UnittestDoc.cpp - the document These files contain your CUnittestDoc class. Edit these files to add your special document data and to implement file saving and loading (via CUnittestDoc::Serialize).

UnittestView.h, UnittestView.cpp - the view of the document These files contain your CUnittestView class. CUnittestView objects are used to view CUnittestDoc objects.

/////////////////////////////////////////////////////////////////////////////

Other files:

StdAfx.h, StdAfx.cpp These files are used to build a precompiled header (PCH) file named Unittest.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.

Unittest.manifest 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.

TTYWindow.cpp TTYWindow.h VS c++ 2013 wizard dialog box for displaying text output.

///////////////////////////////////////////////////////////////////////////// Other notes:

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, you will need to redistribute the MFC DLLs. If your application is in a language other than the operating system's locale, you will also have to redistribute the corresponding localized resources mfc110XXX.DLL. For more information on both of these topics, please see the section on redistributing Visual C++ applications in MSDN documentation.

/////////////////////////////////////////////////////////////////////////////