Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / microsoft/vs-azure-iot-edge-docs issues and pull requests
#48 - Visual Studio 2022: iotedgehubdev.exe start vs modulecred
Issue -
State: open - Opened by fmondelo 11 months ago
#48 - Visual Studio 2022: iotedgehubdev.exe start vs modulecred
Issue -
State: open - Opened by fmondelo 11 months ago
#47 - When trying to generate new modules nothing happens
Issue -
State: open - Opened by AnOdyssey about 1 year ago
- 5 comments
#47 - When trying to generate new modules nothing happens
Issue -
State: open - Opened by AnOdyssey about 1 year ago
- 5 comments
#46 - Documentation out of date for maintenance
Issue -
State: open - Opened by tank104 over 1 year ago
- 1 comment
#46 - Documentation out of date for maintenance
Issue -
State: open - Opened by tank104 over 1 year ago
- 1 comment
#45 - Older Versions of Azure IoT Edge Tools Visual Studio Extensions
Issue -
State: closed - Opened by scout208 over 1 year ago
- 1 comment
#45 - Older Versions of Azure IoT Edge Tools Visual Studio Extensions
Issue -
State: closed - Opened by scout208 over 1 year ago
- 1 comment
#44 - Azure IoT Edge Tools for VS 2022 is generating the tmp_deployment_for_local_debug.json file from deployment.template.json instead of deployment.debug.template.json
Issue -
State: open - Opened by miniGweek over 2 years ago
- 1 comment
#43 - Please add support for IoT Edge Runtime 1.4 to the Azure IoT Edge Tools for VS 2022
Issue -
State: open - Opened by miniGweek over 2 years ago
- 3 comments
#42 - Announcing the Azure IoT Edge tool offerings in maintenance mode
Issue -
State: closed - Opened by konichi3 over 2 years ago
- 11 comments
#41 - This repo is missing important files
Issue -
State: closed - Opened by microsoft-github-policy-service[bot] over 2 years ago
#40 - Adding Microsoft SECURITY.MD
Pull Request -
State: closed - Opened by microsoft-github-policy-service[bot] over 2 years ago
#39 - Please take the survey to help us shape our Azure IoT Edge tool offering
Issue -
State: closed - Opened by konichi3 almost 3 years ago
#38 - VS 2022 templates still refer to .NET Core 3.1
Issue -
State: open - Opened by algorni almost 3 years ago
- 1 comment
Labels: InBacklog
#37 - new version
Pull Request -
State: closed - Opened by mhshami01 almost 3 years ago
#36 - Unable to deploy to devices since CLoud Explorer is Retired
Issue -
State: closed - Opened by Andkago about 3 years ago
- 2 comments
Labels: InBacklog
#35 - VS2022 Support?
Issue -
State: closed - Opened by chull434 about 3 years ago
- 17 comments
Labels: InBacklog
#34 - Fix link to VS 2019 Extension
Pull Request -
State: closed - Opened by raspher about 3 years ago
#33 - Azure IoT Edge Tools for VS 2019 v2.0.0: Could not load file or assembly Microsoft.VisualStudio.Validation, Version=16.9.0.0
Issue -
State: closed - Opened by felixmondelo over 3 years ago
- 2 comments
Labels: InBacklog
#32 - Azure IoT Edge Tools for VS 2019 v1.9.0: Automatic edit of files each time the project is opened
Issue -
State: closed - Opened by martin-weber over 3 years ago
- 4 comments
#31 - "Build IoT Edge Modules" does not use module.json buildOptions
Issue -
State: open - Opened by vermillionsword over 3 years ago
- 5 comments
Labels: InBacklog
#30 - Unable to deploy MQTT enabled IoT edge hub using Azure IoT Edge Tools for VS 2019 v1.7
Issue -
State: open - Opened by ajaykush almost 4 years ago
- 1 comment
Labels: enhancement, InBacklog
#29 - Various inconsistencies related to targeted configuration and multiple modules
Issue -
State: open - Opened by Salazander almost 4 years ago
- 1 comment
Labels: bug, InBacklog
#28 - ModuleNotFoundError: No module named 'pkg_resources.py2_warn'
Issue -
State: closed - Opened by longday24 about 4 years ago
- 6 comments
#27 - Simulated Temperature Sensor not configured correctly
Issue -
State: closed - Opened by MichaelVach over 4 years ago
- 2 comments
#26 - Cannot debug any debug any project from VS's UI when this is enabled
Issue -
State: closed - Opened by shizn over 4 years ago
- 3 comments
#25 - Azure IoT Edge Tools for VS 2019 - "Build IoT Edge Modules" command ignoring build args specified in module.json
Issue -
State: closed - Opened by BinaryMike almost 5 years ago
- 3 comments
Labels: Obsolete
#24 - Latest extension targets older Net Core
Issue -
State: closed - Opened by thnk2wn almost 5 years ago
- 4 comments
#23 - Access Denied error when starting iotedgehubdev on VS2019
Issue -
State: closed - Opened by SaravananGajendran about 5 years ago
- 2 comments
#22 - Default routes always added when opening visual studio
Issue -
State: closed - Opened by mrtncls about 5 years ago
- 5 comments
#21 - the first letter of module name is missing in simulator output logs
Issue -
State: closed - Opened by czgtest about 5 years ago
- 2 comments
#20 - Run IoT edge simulator fail when update DOCKER_HOST as npipe:////./pipe/iotedge_moby_engine
Issue -
State: closed - Opened by czgtest about 5 years ago
- 1 comment
#19 - Don't show output from "package manager" when create new project
Issue -
State: closed - Opened by czgtest about 5 years ago
- 1 comment
#18 - install simulator failed when set docker_host to "tcp://10.172.15.01:2375"
Issue -
State: closed - Opened by czgtest about 5 years ago
- 1 comment
#17 - Cannot create a file when that file already exists when update iot edge simulator
Issue -
State: closed - Opened by czgtest about 5 years ago
- 2 comments
#16 - Module Twin support when setup the IoT Edge Simulator
Issue -
State: closed - Opened by czgtest about 5 years ago
- 1 comment
#15 - SimulatedTemperatureSensor module Will not automatically add to default project
Issue -
State: closed - Opened by czgtest about 5 years ago
- 1 comment
#14 - Azure IoT Edge Tools for VS 2019 - Create new IoT Edge project with a C# module - Error
Issue -
State: closed - Opened by jonmikeli about 5 years ago
- 15 comments
#13 - docker build fails - when reference library/shared code in project/solution
Issue -
State: closed - Opened by grahamehorner about 5 years ago
- 3 comments
#12 - Default template should not include SimulatedTemperatureSensor
Issue -
State: closed - Opened by rido-min about 5 years ago
- 2 comments
#11 - IOT Edge tools break debugging
Issue -
State: closed - Opened by Joehannus over 5 years ago
- 3 comments
#10 - configurable Docker-Root-Directory
Issue -
State: closed - Opened by burgerTo over 5 years ago
- 5 comments
#9 - Cannot Add a FunctionsModule in VS2019
Issue -
State: closed - Opened by Fredborg over 5 years ago
- 2 comments
Labels: Obsolete
#8 - Build Edge solution with Visual Studio 2019 BuildTools
Issue -
State: closed - Opened by cmenzi over 5 years ago
- 6 comments
#7 - Azure Marketplace broken?
Issue -
State: closed - Opened by jkewley over 5 years ago
- 1 comment
#6 - Modules in subfolders don't start when debugging IoT Edge project
Issue -
State: closed - Opened by candersonio over 5 years ago
- 2 comments
#5 - Debugging disabled for .NET Core projects after installing plugin
Issue -
State: closed - Opened by heing over 5 years ago
- 3 comments
#4 - NU 1202 Error when creating projects from Template
Issue -
State: closed - Opened by ray-linn over 5 years ago
- 2 comments
#3 - Problem remains: Unable to load the service index for source https://api.nuget.org/v3/index.json
Issue -
State: closed - Opened by hubert-associates over 5 years ago
- 5 comments
#2 - Add remote debug support
Issue -
State: closed - Opened by adashen over 5 years ago
- 2 comments
#1 - VS IoT Edge Tools for VS 2019
Issue -
State: closed - Opened by mjrousos over 5 years ago
- 1 comment