The AllJoyn Device System Bridge (DSB) provides developers with a way to easily bring non-AllJoyn devices into the AllJoyn ecosystem. It does so by using existing device interfaces to access the non-AllJoyn devices and creates a virtual proxy for these devices on the AllJoyn bus. Thanks to the AllJoyn DSB, AllJoyn and non-AllJoyn devices can now interact seamlessly. For more information visit https://developer.microsoft.com/en-us/windows/iot/docs/alljoyndsb
Universal Windows Platform (UWP) templates are provided to enable building AllJoyn Device System Bridges for C# and C++/CX projects using Visual Studio 2015. If you are looking for templates for Visual Studio 2017, use this link instead.
How to create a Device System Bridge
Open a new project: File -> New -> Project
In the project dialog, navigate the Installed project templates to Visual C ++ -> Windows or to Other Languages -> Visual C# -> Windows, and select AllJoyn Device System Bridge.
Name your project and press OK.
Visual Studio will automatically create the DSB project structure in your solution.
The solution has several projects. Each project is briefly described below:
HeadlessAdapterApp
The HeadlessAdapterApp wraps the Adapter and the Bridge and creates an AllJoyn Device System Bridge Universal App running in the background without User Experience on Windows 10 IOT Core.
HeadedAdapterApp
The HeadedAdapterApp wraps the Adapter and the Bridge in a manner that creates an AllJoyn Device System Bridge Universal App with UI capabilities to run on Windows 10 (as opposed to the HeadlessAdapterApp, which has no UI and can run on Windows 10 IOT Core as a Background Application).
AdapterLib
Here is where you include your code. The AdapterLib communicates with and abstracts physical devices such that the Bridge can expose this abstraction to the AllJoyn bus.
BridgeRT
The BridgeRT component exposes the non-AllJoyn devices to the AllJoyn bus using the AllJoyn API. Devices come from AdapterLib, and BridgeRT projects them on AllJoyn bus.