<< Click to Display Table of Contents >> Navigation:  Deployment > Windows based deployment

DDK Drivers can be deployed and run using normal BNCS tooling such as Workstation Manager etc.

 

We recommend that each DDK driver is deployed in its own sub-directory of the drivers binary directory - this is to ensure that differing dependency versions don't conflict.  Alternatively, the Visual Studio publish tools can be used to generate a self contained executable file although these tend to be quite large and so not as efficient when synced from a central file server.

 

Although the DDK can be used to build applications with a UI, we strongly advise against this approach and recommend sticking to console applications that can then have a common code base with containerised variants.  Multiple console based drivers on a single machine can lead to confusion though so we recommend that the DDK Driver Viewer application be installed in local mode on each Windows machine hosting DDK drivers.  This provides a single web interface to all the DDK drivers running on the machine.  Refer to the DDK Driver Viewer documentation for deployment instructions.