From 370eea92d99e4a58d4bbad4e4bb6af87193a6c1b Mon Sep 17 00:00:00 2001 From: Matt Cooley Date: Tue, 4 Jan 2022 08:07:41 -0800 Subject: [PATCH] Remove NuGetCommand workaround in YAML (#1762) --- build/pipelines/templates/build-single-architecture.yaml | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/build/pipelines/templates/build-single-architecture.yaml b/build/pipelines/templates/build-single-architecture.yaml index 5a12cb7..f29c693 100644 --- a/build/pipelines/templates/build-single-architecture.yaml +++ b/build/pipelines/templates/build-single-architecture.yaml @@ -48,9 +48,7 @@ jobs: inputs: versionSpec: 5.x - # In most accounts, you can just use 'NuGetCommand' instead of this GUID. - # In the microsoft.visualstudio.com account, NuGetCommand is ambiguous so the GUID is needed. - - task: 333b11bd-d341-40d9-afcf-b32d5ce6f23b@2 + - task: NuGetCommand@2 displayName: NuGet restore src/Calculator.sln inputs: command: custom @@ -126,4 +124,4 @@ jobs: - task: ms.vss-governance-buildtask.governance-build-task-component-detection.ComponentGovernanceComponentDetection@0 displayName: Detect open source components inputs: - sourceScanPath: $(Agent.BuildDirectory) \ No newline at end of file + sourceScanPath: $(Agent.BuildDirectory)