If you are a container expert, you may want to port your existing compose application to Azure IoT Edge. We are glad to introduce iotedge-compose to help convert your docker-compose project to Azure IoT Edge. Let us see how it works.
Use containerized device tool chain in Azure IoT Device Workbench to simplify device tool chain acquisition challenge.
Azure IoT Edge Tools (Preview) for Visual Studio 2017 allows you to easily develop and debug Azure IoT Edge modules locally. To learn how to use this extension to develop and debug Edge module locally, you can refer these documents:
Easily Develop and Debug Azure IoT Edge C Modules with Azure IoT Edge Tools
Use Visual Studio 2017 to develop and debug modules for Azure IoT Edge (Preview)
Together with the new Azure IoT Tools for VS Code extension pack, we also overhauled the experience of Azure IoT Device Workbench. And there is another exciting sample contributed by Chris Lovett (Github) from Microsoft Research about running Embedded Learning Library (ELL) on MXChip IoT DevKit to achieve the keyword spotting locally.
Now Azure IoT Edge for VS Code 1.6.0 has been released with a bunch of new features.
We are proud to announce the availability of the Azure IoT Edge plugin for Jenkins, which provides Jenkins native capability to continuously build IoT Edge solutions and deploy to Azure IoT Edge devices. Depending on your environment, you can choose to use Azure DevOps Services together with Jenkins,
IoT Application Development is naturally more complicated than regular application development, in that even the simplest E2E IoT application involves a long chain from device layer, to communication layer, then to the cloud and beyond. This makes the development especially the testing and debugging difficult.