Integrate with your app


Contents

1. Required libraries

2. Configuration

3. SDK footprint

After having some hands-on experience with our SDK from the previous guides, the next step is to integrate Zoom Windows SDK in your own applications and power your applications with Zoom’s audio and video conferencing features.

1. Required libraries

When developing your application, using our Windows SDK requires the files inside the following folders:

  • \lib
  • \h
  • \bin

When you are releasing/publishing your application, you only need to include the files inside \bin.

2. Configuration

In your project’s Configuration Properties:

  1. Navigate to the General subtab, and set the path for the Output Directory and Intermediate Directory to …\bin.
  1. Go to VC++ Directories:
    • Append …\h to Include Directories
    • Append …\lib to Library Directories
  1. Next, under the Linker subtab, select General:
    • Change Output file to any location you would like the output file to be stored.
  1. In C/C++
    • Change “Debug Information Format” to None

After importing the libraries and header files, now you can start using Zoom services inside your Windows applications.

Please do not re-sign/assign a new digital signature to the following files as assigning new digital signature on these files could lead to fatal errors:

  • CptControl.exe
  • CptHost.exe
  • CptInstall.exe
  • CptService.exe
  • CptShare.dll
  • zzhost.dll
  • zzplugin.dll
  • aomhost64.exe

3. SDK footprint

Our SDK includes rich features in video conferencing. The overall size of our Windows SDK is around 52MB.

4. Creating an installer and publishing

Follow official documentation for packaging a C++ app for Windows and complete the following additional steps.

  1. After importing the libraries and header files, run the command cptinstall.exe -uninstall with administrator privileges. This step is to ensure that users who have installed an older package can use the share function normally. Now you can start using Zoom services inside your Windows applications.

  2. If publishing your app, copy the following Microsoft runtime libraries to bin and bin/aomhost directories.

concrt140.dll
msvcp140.dll
msvcp140_1.dll
msvcp140_2.dll
msvcp140_codecvt_ids.dll
vccorlib140.dll
vcruntime140.dll 
api-ms-win-core-console-l1-1-0.dll 
api-ms-win-core-console-l1-2-0.dll 
api-ms-win-core-datetime-l1-1-0.dll 
api-ms-win-core-debug-l1-1-0.dll 
api-ms-win-core-errorhandling-l1-1-0.dll 
api-ms-win-core-file-l1-1-0.dll 
api-ms-win-core-file-l1-2-0.dll 
api-ms-win-core-file-l2-1-0.dll 
api-ms-win-core-handle-l1-1-0.dll 
api-ms-win-core-heap-l1-1-0.dll 
api-ms-win-core-interlocked-l1-1-0.dll 
api-ms-win-core-libraryloader-l1-1-0.dll 
api-ms-win-core-localization-l1-2-0.dll 
api-ms-win-core-memory-l1-1-0.dll 
api-ms-win-core-namedpipe-l1-1-0.dll 
api-ms-win-core-processenvironment-l1-1-0.dll 
api-ms-win-core-processthreads-l1-1-0.dll 
api-ms-win-core-processthreads-l1-1-1.dll 
api-ms-win-core-profile-l1-1-0.dll 
api-ms-win-core-rtlsupport-l1-1-0.dll 
api-ms-win-core-string-l1-1-0.dll 
api-ms-win-core-synch-l1-1-0.dll 
api-ms-win-core-synch-l1-2-0.dll 
api-ms-win-core-sysinfo-l1-1-0.dll 
api-ms-win-core-timezone-l1-1-0.dll 
api-ms-win-core-util-l1-1-0.dll 
API-MS-Win-core-xstate-l2-1-0.dll 
api-ms-win-crt-conio-l1-1-0.dll 
api-ms-win-crt-convert-l1-1-0.dll 
api-ms-win-crt-environment-l1-1-0.dll 
api-ms-win-crt-filesystem-l1-1-0.dll 
api-ms-win-crt-heap-l1-1-0.dll 
api-ms-win-crt-locale-l1-1-0.dll 
api-ms-win-crt-math-l1-1-0.dll 
api-ms-win-crt-multibyte-l1-1-0.dll 
api-ms-win-crt-private-l1-1-0.dll 
api-ms-win-crt-process-l1-1-0.dll 
api-ms-win-crt-runtime-l1-1-0.dll 
api-ms-win-crt-stdio-l1-1-0.dll 
api-ms-win-crt-string-l1-1-0.dll 
api-ms-win-crt-time-l1-1-0.dll 
api-ms-win-crt-utility-l1-1-0.dll 
ucrtbase.dll