Building the Set of Sample Applications

All the sample applications are shipped in two forms: as compiled, executable files and as source files. You can rebuild the sample applications as a set or individually. Rebuilding the sample applications is useful for the following purposes:

• Creates a set of sample applications with the DEBUG build type. This allows you to extract more information about the sample applications from the Visual C++ interface.
• Acts as a test of your development environment.
• Simplifies the process of building a complex sample application that requires several other sample applications to be built before it can run.

You will need Visual C++ version 4.0 or later on your system, which can be used to compile both C and C++ files and must be part of the development environment.

A WIN32 subdirectory is added below the current directory for each sample application. A subdirectory is added below the WIN32 subdirectory for the build type. For example, if the build type is DEBUG, this subdirectory is called DEBUG. All object files, .LIB files, and output files are placed in the build type subdirectory. In this way, DEBUG and RETAIL versions of a product can exist simultaneously in the same directory tree.

    To build the set of all sample applications

1. Change to the directory containing the sample applications:

   \BKOFFICE\SAMPLES\EXCHANGE

2. Type NMAKE [BLDTYPE=RETAIL].

   This command builds each library in order, then combines all the libraries into the ExchSDKd.LIB library (DEBUG) or the ExchSDK.LIB library (RETAIL).

Building all the sample applications may take 45 to 60 minutes. If stopped, then restarted, the process will compare all products and build only those that have changed since the last time it was invoked. In essence, the process will restart from where it stopped.