Quantcast
Channel: Active questions tagged nuget-package - Stack Overflow
Viewing all articles
Browse latest Browse all 3067

Azure Pipelines: Fail to use DotNetCoreCLI custom command

$
0
0

I struggle to allow for debugging my own nuget packages hosted on azure.I tried quite a few things since this is apparently a common problem with many ways to address.Classic pipeline like this worked (yaml view):

- task: DotNetCoreCLI@2  displayName: 'Create NuGet Packages'  inputs:    command: pack    packagesToPack: '**/*.csproj;!**/*.Tests.csproj'    packDirectory: Solution/Packages    nobuild: true    includesymbols: true    includesource: true

but at the end debugging still would not work.Then I came across this article: https://docs.microsoft.com/en-us/nuget/create-packages/symbol-packages-snupkgBut now I keep failing running my .net cli custom command.I simply don't know how to specify my project(s) to be packed as arguments.Anything I tried failed:

- task: DotNetCoreCLI@2  displayName: 'dotnet custom'  inputs:    command: custom    custom: 'dotnet pack **/*.csproj;!**/*.Tests.csproj -p:IncludeSymbols=true -p:SymbolPackageFormat=snupkg'

I tried a few paths without wildcards but the problem is I do not even know which (relative) path to use. I tried quite a few paths but none worked.How do I pass arguments like project paths?


Viewing all articles
Browse latest Browse all 3067

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>