Sample Source Code

Code samples are fully operational to the best of my knowledge. If you find any bugs or have something to suggest about the samples, please feel free to write me at niko@wrconsulting.com. Samples are organized by chapters, and the text in the book refers to the samples by project name where applicable.

All Visual Basic based projects have a Vb prefix. For example, if a node in the source code tree is named VbDumpTokenComTester, then it was created with Visual Basic.
 

A Note about C++ Samples

There are several possible project configurations for C++ projects available via the Build - Set Active Configuratuion menu. For example, when creating a brand new COM object using ATL COM AppWizard the choices are: Win32 Debug, Win32 Unicode Debug, Win32 Release MinSize, Win32 Release MinDependency, Win32 Unicode Release MinSize, and Win32 Unicode Release MinDependency. Some of these configurations may be removed (using the Build - Configurations menu). You can also create new ones (configurations with different names), based on existing ones. To make things simple I have decided to keep only 2 configurations available for my C++ samples: Debug (based on Win32 Debug), and Release (based on Win32 Release MinSize). This should simplify sample code distribution and builds because you don't have to struggle with the Win32 Unicode Release MinDependency issue. This is the last configuration in the default list. It gets selected automatically if the configuration list is unchanged. This happens because the <ProjectName>.opt file is not distributed with the source files.