Programming with the Toolkit Features

Kinect for Windows 1.5, 1.6, 1.7, 1.8

Several of the new features in version 1.7 are provided as Toolkit components, not as SDK components. Toolkit components, unlike SDK components, do not end up in the managed GAC or in Windows\System32 or any other directory that ends up in the system path by default.

Developers will need to do a little more work to make sure that these binaries end up where they need them to be during build and when their application is deployed.

One method is to include the relevant components as part of your project, as is done in the Kinect Fusion C++ samples, and in the InteractionGallery - WPF and Controls Basics-WPF managed samples.

Whichever approach you wish to use, during application deployment, you need to make sure the application can find the dlls.

For Kinect Interaction applications, please make sure that Microsoft.Kinect.Toolkit.Interaction.dll, KinectInteraction170_32.dll and KinectInteraction170_64.dll binaries end up in a file system path where the application will find them. KinectInteraction170_32.dll and KinectInteraction170_64.dll are in %KINECT_TOOLKIT_DIR%Redist\{x86|amd64} directories. Microsoft.Kinect.Toolkit.Interactions.dll is in %KINECT_TOOLKIT_DIR%assemblies

Community Additions