Check existing project names when adding new module to avoid exception
Rename tempSensor to SimulatedTemperatureSensor in deployment template file
Fix the issue that module in solution folder cannot start debugger correctly
What's New (v1.1.1)
Fix marketplace cannot load issue
What's New (v1.1)
Add dialog to help user to setup device connection string when start simulator failed
Allow environment variables in image URL
Use obj folder to store local debug json file
Automatically stop simulator when terminate debugger
Fix high DPI issue of description text in add module dialog
What's New (v1.0)
Remove preview label and update document
Enable adding modules from Azure marketplace
Use deployment.debug.template.json to support Debug configuration for IoT Edge project
Enable schema validation for deployment template file
Fix some bugs
What's New (v0.5.1)
Remove the dependency on Nuget package Microsoft.VisualStudio.Azure.IoT.Edge.MSBuildTasks for IoT Edge project
Allow switch among supported platforms (Linux amd64/Linux arm32v7/Windows amd64) for IoT Edge project
Support relative path for image of module in deployment template file
Support environment variables in module.json
Move "Target Platform"/"Target Configuration" of IoT Edge Project from Properties Pages to Properties Windows
Fix some bugs
NOTE: The IoT Edge project created by this version(>=0.5) could not be opened by previous versions.
What's New (v0.4.5)
Use different project templates for different platforms
Support environment variables in deployment.template.json
Automatically add environment and .env for private registry during adding module
What's New (v0.4.0)
Set DOCKER_HOST in Tools->Options->IoT Edge Tools
What's New (v0.3.1)
Support C Module
What's New (v0.2.0)
Add support for multiple deployment projects (.iotedgeproj) in one solution. Now each .iotedgeproj will only support one arch,
you need to add multiple .iotedgeproj if need to support multiple arch.
What's New (v0.1.7)
Update your existing IoT Edge projects to refer to nuget package Microsoft.VisualStudio.Azure.IoT.Edge.MSBuildTasks to latest version 0.1.4
What's New (v0.1.5)
Add contextPath in module.json to support docker build context, contextPath is relative path based the folder containing module.json
Visual Studio 2017 15.7 or higher.
".NET desktop development" and "Azure development workload" workload installed; "Windows desktop development with C++" is needed if you plan to develop C modules.
Docker Community Edition on your development machine to build and run your module images. You need to properly set the Docker CE running in Linux container mode or Windows container mode.
To set up local development environment to debug, run, and test your IoT Edge solution, you need Azure IoT EdgeHub Dev Tool. Install Python (2.7/3.6) and Pip. Then install iotedgehubdev by running below command in your terminal. Make sure your Azure IoT EdgeHub Dev Tool version is greater than 0.3.0.