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.

Can't run dotnet pack with sources/symbols when project uses Paket

See original GitHub issue

Description

I get an error when running dotnet pack with the --include-symbols and --include-source arguments.

\.paket\Paket.Restore.targets(100,5): error : The given path's format is not supported.

Everything works when dropping these arguments. One strange thing that also happens is that if you build it with the arguments then the build without arguments also fails until you delete the symbols.nuspec file in the obj folder.

Repro steps

Repro: PaketRepro.zip

Extract the repo and go to the root Stuff.Repro
Run dotnet pack --include-symbols or dotnet pack --include-source

Expected behavior

The command should output a nuget package for the project and one for the symbols

Actual behavior

Throws error \.paket\Paket.Restore.targets(100,5): error : The given path's format is not supported.

Known workarounds

None

Environment

Paket version: 5.91.0 .Net SDK version: 2.0.0 OS: Windows 10

Issue Analytics

State:
Created 6 years ago
Reactions:2
Comments:8 (3 by maintainers)

Top GitHub Comments

2reactions

purkhusidcommented, Sep 2, 2017

Pull request here: https://github.com/fsprojects/Paket/pull/2711

1reaction

PMudracommented, Oct 29, 2018

Site note for anybody that just wants to add the *.pdb into the main nuget package:

<AllowedOutputExtensionsInPackageBuildOutputFolder>$(AllowedOutputExtensionsInPackageBuildOutputFolder);.pdb</AllowedOutputExtensionsInPackageBuildOutputFolder>

https://stackoverflow.com/a/48391188 https://github.com/NuGet/Home/issues/4142

Top Results From Across the Web

dotnet pack command - .NET CLI

Prints out a description of how to use the command. --include-source. Includes the debug symbols NuGet packages in addition to the regular NuGet ......

Add a package with a local package file in 'dotnet'

The package foo.1.0.0.nupkg has been created with dotnet pack in a different project. The command dotnet add package however tries to download ...

paket pack

A dependency manager for .NET with support for NuGet packages and git repositories.

NuGet packages in the Package Registry

Set a project-level endpoint. Publish a package by running this command: dotnet nuget push <package_file> --source <source_name>.

Publishing debug symbols — Making debugging available ...

I'll go through how to publish the package and symbols to NuGet feeds at: ... The dotnet CLI can be use to create...