AllJoyn® in Windows® 10
An AllJoyn® development toolkit to quick-start AllJoyn® development.
The AllSeen Alliance created AllJoyn® to empower the Internet of Things to transcend devices, ecosystems and the "walled gardens" that typically limit interoperability to devices within a product family.
Windows® 10 has AllJoyn® built natively into its platform, allowing developers to easily IoT-enable their apps and devices. Notably, Windows® 10 provides an AllJoyn® WinRT API, and an AllJoyn® code generator is included in the Windows® 10 SDK. Together, these enable intuitive interaction with AllJoyn®-enabled devices.
AllJoyn® Studio accelerates AllJoyn® development by combining code generation and the WinRT API with automated project management and ready-made application templates. It allows developers to benefit from the power of AllJoyn without the hassle of set-up and configuration.
- Automated reference management and project configuration
- Adding/removing interfaces to/from a solution
- Easy access to project management via the AllJoyn® menu
- Loading interfaces from introspection XML file(s)
- Discovering interfaces from producer(s) on the network1
- Visual Studio 2015 (Community, Professional or Enterprise)
- Windows® 7, 8.1 or 10
The AllSeen Alliance created AllJoyn to empower the Internet of Things. Windows 10 has AllJoyn built natively into its platform, allowing developers to easily take advantage of AllJoyn to "IoT-enable" your Windows 10 apps. This article will outline the steps required to build apps for Windows 10 using the Universal Windows Platform (UWP) AllJoyn APIs and the Visual Studio 2015 AllJoyn® Studio Extension.
This blog post is a fulfillment of the promises made in the AllJoyn session presented at //build/ 2015:
Understanding AllJoyn UWP App Development
Three major components form AllJoyn UWP apps:
- The AllJoyn core APIs: AllJoyn Standard Client API (C) and Windows.Devices.AllJoyn API (WinRT) available in the Windows 10 SDK.
- One or more UWP Windows Runtime Components (the generates this code from AllJoyn interfaces).
The following diagram shows the architecture of a typical AllJoyn UWP project:
This blogpost covers the first two ways - AllJoyn® Studio natively supports querying the network for AllJoyn producers and extracting their XML as well as uploading Introspection XML files. A future post will cover the third way.
At //build/ 2015, an AllJoyn-enabled toaster device was shown which will serve as the example for this post. This toaster exposes controls for starting and stopping the toasting sequence, setting the "darkness", and notifications when the toast is burnt.
Also check out;
Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.