Azure / Azure/iotedgedev

iotedgedev solution init hangs at dotnet new -i Microsoft.Azure.IoT.Edge.Module

Open
#632 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
166
Forks
76
PR merge metrics
No merged PRs in 30d

Description

# Description
When running iotedgedev solution init --template csharp, the CLI hangs indefinitely while invoking the module template installer. No error or progress output is shown, and there is no documented verbose flag.

# Environment

iotedgedev version: 3.3.7

.NET SDK version: 8.0.410

Dev Container image: mcr.microsoft.com/iotedge/iotedgedev:latest

# Reproduction Steps

Ensure Microsoft.Azure.IoT.Edge.Module::1.2.0 is installed:

dotnet new install Microsoft.Azure.IoT.Edge.Module::1.2.0
Run scaffolding command:

iotedgedev solution init \
--template csharp \
--environment-variables .env

# Observed Behavior

The process stops at:

===============================================================
======== DOTNET NEW -I MICROSOFT.AZURE.IOT.EDGE.MODULE ========
===============================================================
No progress indicator, no timeout, and no debug output.

# Expected Behavior

Template should install (or detect existing install) and proceed to generate the C# module project.

A --verbose or --debug flag should surface underlying dotnet new logs.

# Troubleshooting Already Tried

Manual install/uninstall of Microsoft.Azure.IoT.Edge.Module v1.2.0 succeeds.

Verified dotnet new --list shows the template.

Tested network connectivity to NuGet (curl https://api.nuget.org/v3/index.json).

# Questions / Help Requested

Is there an undocumented flag to enable verbose logging for the underlying dotnet new call?

Could this be caused by a version mismatch between iotedgedev and .NET 8?

Any additional diagnostics I can enable to capture why the template installer is hanging?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.