Error from package creation when building .NET SDK projects
See original GitHub issueDescription
We have Paket integrated with the .NET SDK via the bootstrapper in Magic Mode, as recommended. When Paket is invoked as part of the build on a solution containing .NET SDK projects to be packaged for NuGet, some of the projects fail with errors like the following:
C:\code\.paket\Paket.Restore.targets(210,5): error : The filename, directory name, or volume label syntax is incorrect : 'C:\code\test\TestHelpers\obj\Release\TestHelpers.1.0.0-pre-000000.nuspec;C:\code\test\TestHelpers\obj\Release' [C:\code\test\TestHelpers\TestHelpers.csproj]
As far as I can tell based on comparisons between succeeding and failing project files, it doesn’t appear to be anything related to the project file or their target frameworks.
These are the .NET SDK calls being invoked on my machine:
dotnet build --no-cache $SolutionFile -c Release --version-suffix=pre-000000
dotnet publish --no-build $SolutionFile -c Release
On one branch, where I converted from NuGet to paket using the conversion tool, five projects throw this error. On another branch, where I converted from NuGet to paket manually, only three projects throw this error, a subset of the five.
Repro steps
I am not sure of the repro steps in this instance, as it happens on the first attempted build after converting the project to paket.
Expected behavior
Paket packs the projects successfully.
Actual behavior
Some projects fail with errors like the following:
C:\code\.paket\Paket.Restore.targets(210,5): error : The filename, directory name, or volume label syntax is incorrect : 'C:\code\test\TestHelpers\obj\Release\TestHelpers.1.0.0-pre-000000.nuspec;C:\code\test\TestHelpers\obj\Release' [C:\code\test\TestHelpers\TestHelpers.csproj]
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (7 by maintainers)
Top GitHub Comments
@forki
dotnet pack --include-symbols
still fails withpaket version 5.176.6
Tagging in another related issue: #2689