You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a recent user study (unmoderated getting started with azd conducted in Q4 2022), a customer tried azd with a .NET template but didn't have .NET installed. He got the error "failed to initialize secrets at project '/path/to/project/': exec: "dotnet": executable file not found in $PATH," and did try to troubleshoot by Googling, but only looked up the first part ("azd failed to initialize secrets"), which only led him to a closed Github issue related to Azure API. He also tried searching our docs for the word "failed" but was also not able to find any information.
We believe that putting "dotnet" at the front of the error message would make it more obvious what the issue is. Propose to reword this to something like "dotnet": executable file not found in $PATH. failed to initialize secrets at project '/path/to/project/'
Presumably, this would apply to similar messages for other languages too.
The text was updated successfully, but these errors were encountered:
In a recent user study (unmoderated getting started with azd conducted in Q4 2022), a customer tried azd with a .NET template but didn't have .NET installed. He got the error "failed to initialize secrets at project '/path/to/project/': exec: "dotnet": executable file not found in $PATH," and did try to troubleshoot by Googling, but only looked up the first part ("azd failed to initialize secrets"), which only led him to a closed Github issue related to Azure API. He also tried searching our docs for the word "failed" but was also not able to find any information.
We believe that putting "dotnet" at the front of the error message would make it more obvious what the issue is. Propose to reword this to something like "dotnet": executable file not found in $PATH. failed to initialize secrets at project '/path/to/project/'
Presumably, this would apply to similar messages for other languages too.
The text was updated successfully, but these errors were encountered: