question-mark
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.

Error from package creation when building .NET SDK projects

See original GitHub issue

Description

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:open
  • Created 5 years ago
  • Comments:15 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
lexarchikcommented, Aug 17, 2018

@forki dotnet pack --include-symbols still fails with

<...>\.paket\Paket.Restore.targets(213,5): error : The filename, directory name, or volume label syntax is incorrect : '<...>\PackTest2\obj\Debug\PackTest2.1.0.0.nuspec;<...>\PackTest2\obj\Debug' [<...>\PackTest2\PackTest2.csproj]

paket version 5.176.6

0reactions
aaronpowellcommented, Feb 27, 2019

Tagging in another related issue: #2689

Read more comments on GitHub >

github_iconTop Results From Across the Web

NETSDK1045: The current .NET SDK does not support ...
This error occurs when the build tools can't find the version of the .NET SDK that's needed to build a project. This is...
Read more >
Package not found while building a mixed solution (.NET ...
I get a compilation error when compiling my .NET Core project : C:\Program Files\dotnet\sdk\2.1.301\Sdks\Microsoft.NET.Sdk\targets\Microsoft ...
Read more >
Cannot debug net6.0-macos Apps - Developer Community
When I hit debug, the following error is shown in the Terminal: Possible reasons for this include: * You misspelled a built-in dotnet...
Read more >
Unable to build new project - Radzen Blazor Studio
I just installed the Alpha kit, and created a new server project, which fails to build with the output window showing the error:...
Read more >
Visual Studio 2019 unable to locate .Net Core SDK
Step 1) First run dotnet --list-sdks from the command line (as in Grzegorz Smulko's answer). Take note of the greatest version number.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found