question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

'AzureSignTool.exe' is not recognized as an internal or external command

See original GitHub issue

Required Information

Entering this information will route you directly to the right team and expedite traction.

Question, Bug, or Feature?
Type: Bug

Enter Task Name: DotNetCoreCLI@2

Environment

Issue Description

I’m using DotNetCoreCLI@2 task to install azuresigntool as global tool and I use it in a subsequent CmdLine@2 as AzureSignTool.exe

This worked fine for several builds over several days. Right now, the command line task fails because the tool AzureSignTool.exe does not exists.

I noticed in the latest build this new line from the DotNetCoreCLI@2 task: Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.

Task logs

Successful build: https://dev.azure.com/netoffice/NetOffice/_build/results?buildId=867&view=logs&j=9eeabfde-0b68-5b48-1926-57b56b63f658&t=f675a0b0-bb7e-5e44-da2f-1025e4db31cf

You can invoke the tool using the following command: azuresigntool

Failing build: https://dev.azure.com/netoffice/NetOffice/_build/results?buildId=869&view=logs&j=9eeabfde-0b68-5b48-1926-57b56b63f658&t=f675a0b0-bb7e-5e44-da2f-1025e4db31cf

Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.

I would expect that I can use the tool I install from one task in the subsequent task.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:13 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
jcuzzicommented, Jul 30, 2020

I am running into this exact same issue today…

0reactions
drocxcommented, Sep 1, 2022

Having the same issue as well, I have to redeploy multiple times in order to get this to work which isn’t ideal. any workarounds?

Use the update command instead of install. It sounds weird, but it works.🎉

dotnet tool update --global AzureSignTool

Read more comments on GitHub >

github_iconTop Results From Across the Web

AzureSignTool: command not found - Microsoft Q&A
AzureSignTool : command not found. Hi, I have a step in a simple yaml pipeline to install the Azure Sign Tool. I installed...
Read more >
Windows cmd: 'signtool' is not recognized as an internal or ...
This error means that the SignTool executable is not accessible through cmd.exe . Solution. Add the path for signtool.exe to your system PATH....
Read more >
How to fix "is not recognized as an internal or external ...
'6.0' is not recognized as an internal or external command, operable program or batch file. Your error message might differ slightly ...
Read more >
Why does signtool in command-prompt return "Windows ...
Because the folder isn't in the system PATH . (From the command prompt, type PATH and hit enter to see what the current...
Read more >
AzureSignTool 4.0.1
Azure Sign Tool is similar to signtool in the Windows SDK, with the major difference ... NET tool you can call from the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found