pool:
  name: Azure Pipelines
  vmImage: windows-latest
  demands:
  - msbuild
  - visualstudio
  - vstest

jobs:
- job: Build
  variables:
    BuildSolution: StyleCopAnalyzers.sln
    BuildPlatform: AnyCPU
  strategy:
    matrix:
      Debug:
        BuildConfiguration: Debug
      Release:
        BuildConfiguration: Release
  steps:
  - task: NuGetCommand@2
    displayName: 'NuGet restore'
    inputs:
      restoreSolution: '$(BuildSolution)'

  - task: VSBuild@1
    displayName: 'Build solution StyleCopAnalyzers.sln'
    inputs:
      solution: '$(BuildSolution)'
      platform: '$(BuildPlatform)'
      configuration: '$(BuildConfiguration)'

pool:
  name: Azure Pipelines
  vmImage: windows-latest
  demands:
  - msbuild
  - visualstudio
  - vstest

jobs:
- job: Build
  variables:
    BuildSolution: StyleCopAnalyzers.sln
    BuildPlatform: AnyCPU
  strategy:
    matrix:
      Debug:
        BuildConfiguration: Debug
      Release:
        BuildConfiguration: Release
  steps:
  - task: NuGetToolInstaller@0
    displayName: 'Use NuGet 5.3.1'
    inputs:
      versionSpec: 5.3.1

  - task: NuGetCommand@2
    displayName: 'NuGet restore'
    inputs:
      restoreSolution: '$(BuildSolution)'
      feedsToUse: 'config'
      nugetConfigPath: '$(Build.WorkingDirectory)/NuGet.config'

  - task: VSBuild@1
    displayName: 'Build solution StyleCopAnalyzers.sln'
    inputs:
      solution: '$(BuildSolution)'
      platform: '$(BuildPlatform)'
      configuration: '$(BuildConfiguration)'

Update to NuGet 5.3.1 and configure feeds
Update to NuGet 5.3.1 and configure feeds

The default tool was even older than 4.4.1. For some reason, Azure
Pipelines defaulted to changing the NuGet packages configuration even
though the repository contains a NuGet.config. Update the NuGetCommand
task to not use the invalid defaults it provided.
