The \Source\ folder contains the Visual CADD API declarations in H files. They should be copied to your project folder for inclusion in your C/C++ projects. When used with the sample C++ project, the \Source\ folder should be a sibling folder to the \Examples\ folder.
The \Examples\ folder contains sample C++ projects to build Visual CADD add-on tools in a standard DLL. The sample projects require Visual Studio 2015 through 2022 and the platform toolset v140. With some modifications, all sample projects may be upgraded for more recent platform toolsets. Visual Studio 2022 Community is available as a free download from Microsoft. The source code can be ported to any other C/C++ compiler, as needed.
You may copy the project files and the corresponding folder structure to any local folder for development. The project expects the same relative folder structure of the download, namely that \Source\ and \Examples\ are sibling folders and the project folder is under \Examples\. You may change that structure as long as the project is changed to find the relative locations of the required files in \Source\.
The output from the project is directed to an \Addons\API_Help\ folder as a sibling to the Visual CADD \Programs\ folder, usually C:\Program Files (x86)\TriTools Partners\Visual CADD 9\Addons\API_Help or C:\Program Files\... on 32-bit Windows. The \Addons\ folders are locations Visual CADD automatically searches for executables and CmdExt.vcdef for add-on tools. Thus, the \Addons\API_Help\ folder is a convenient destination for compiled output for development, testing, and deployment.
The same \Addons\API_Help\ folder would normally contain a CmdExt.vcdef
with any custom commands required to run the custom add-on tools.
For example, a CmdExt.vcdef might include:
<Commands> <Command Name="HelloWorldC"> <Script>DllName;API_Help_C.dll;DllFunName;HelloWorld;DllRun;</Script> </Command> </Commands>