dotnet pack "Path to csproj or nuspec file(s) to pack" doesn't work as expected

[nandun5]

Required Information

Question, Bug, or Feature?
Type: Bug

Enter Task Name: DotNetCoreCLI@2
dotnet pack command

Environment

• Server - Azure Pipelines

• Agent - Hosted
  HostedVS2017

Issue Description

The task fails when we specify a nuspec file in the "Path to csproj or nuspec file(s) to pack" field. this is the Yaml version what the UI generates:

steps:
- task: DotNetCoreCLI@2
  displayName: 'dotnet pack'
  inputs:
    command: pack
    packagesToPack: '**/*.nuspec'
    nobuild: true
    versioningScheme: byBuildNumber
  enabled: false

Errorlogs

"C:\Program Files\dotnet\dotnet.exe" pack D:\a\1\s\BBI.PoseidonEnterprise.DataAccess.Orders\BBI.PoseidonEnterprise.DataAccess.Orders.nuspec --output D:\a\1\a /p:Configuration=release /p:PackageVersion=1.0.0.2 --verbosity Detailed
Microsoft (R) Build Engine version 16.7.0+7fb82e5b2 for .NET
Copyright (C) Microsoft Corporation. All rights reserved.

Build started 10/7/2020 3:49:15 PM.
     0>Process = "C:\Program Files\dotnet\dotnet.exe"
       MSBuild executable path = "C:\Program Files\dotnet\sdk\3.1.402\MSBuild.dll"
       Command line arguments = ""C:\Program Files\dotnet\sdk\3.1.402\MSBuild.dll" -maxcpucount -verbosity:m -restore -target:pack -property:PackageOutputPath=D:\a\1\a -verbosity:Detailed D:\a\1\s\BBI.PoseidonEnterprise.DataAccess.Orders\BBI.PoseidonEnterprise.DataAccess.Orders.nuspec /p:Configuration=release /p:PackageVersion=1.0.0.2 "-distributedlogger:Microsoft.DotNet.Tools.MSBuild.MSBuildLogger,C:\Program Files\dotnet\sdk\3.1.402\dotnet.dll*Microsoft.DotNet.Tools.MSBuild.MSBuildForwardingLogger,C:\Program Files\dotnet\sdk\3.1.402\dotnet.dll""
       Current directory = "D:\a\1\s\BBI.PoseidonEnterprise.DataAccess.Orders"
       MSBuild version = "16.7.0+7fb82e5b2"
     1>Project "D:\a\1\s\BBI.PoseidonEnterprise.DataAccess.Orders\BBI.PoseidonEnterprise.DataAccess.Orders.nuspec" on node 1 (Restore target(s)).
     1>Building with tools version "Current".
     1>D:\a\1\s\BBI.PoseidonEnterprise.DataAccess.Orders\BBI.PoseidonEnterprise.DataAccess.Orders.nuspec(2,1): error MSB4068: The element <package> is unrecognized, or not supported in this context.
     1>Done Building Project "D:\a\1\s\BBI.PoseidonEnterprise.DataAccess.Orders\BBI.PoseidonEnterprise.DataAccess.Orders.nuspec" (Restore target(s)) -- FAILED.

Build FAILED.

       "D:\a\1\s\BBI.PoseidonEnterprise.DataAccess.Orders\BBI.PoseidonEnterprise.DataAccess.Orders.nuspec" (Restore target) (1) ->
         D:\a\1\s\BBI.PoseidonEnterprise.DataAccess.Orders\BBI.PoseidonEnterprise.DataAccess.Orders.nuspec(2,1): error MSB4068: The element <package> is unrecognized, or not supported in this context.

    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:00.07
##[error]Error: The process 'C:\Program Files\dotnet\dotnet.exe' failed with exit code 1
##[error]An error occurred while trying to pack the files.

Troubleshooting

this seems to be because the dotnet pack tasks expects a csproj or sln. and the nuspec has to be provided with -p:NugetConfig.

this command line works for us
dotnet pack solution1.sln -p:NugetConfig=Project1\Project1.nuspec

how ever the equivalent of this command that the pipeline dotnet task seem to execute is
dotnet pack Project1\Project1.nuspec

Expected behavior

task should not fail when "Path to csproj or nuspec file(s) to pack" field is populated with a nuspec file.

[bishal-pdMSFT]

@NinadKavimandan

[NinadKavimandan]

Hi @nandun5 - how will be using this task with nuspec file? will you be providing only nuspec file in the command, or do you want to include .sln file as well?

[nandun5]

we are providing the nuspec file with a wildcard as **/*.nuspec

[NinadKavimandan]

okay. is the nuspec file taking care of the files to be packaged? so the command won't need the project/sln path?

[nandun5]

thats correct. in our pipelines, we only specify the nuspec file.

[NinadKavimandan]

alright! thanks.

[tiwarishub]

Hi @nandun5 , we have merged the fix . Please let us know if you are still seeing this issue

[tiwarishub]

Closing as this is resolved