Fix C# workflow NU5017 packaging error #145
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adding CLAUDE.md with task information for AI processing. This file will be removed when the task is complete. Issue: #142
- Remove conflicting DebugType=embedded setting that prevented symbol package creation - Symbol packages now generate successfully with snupkg format - Update release notes to reflect the fix 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
konard
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixed the C# workflow failure caused by NU5017 packaging error: "Cannot create a package that has no dependencies nor content".
Root Cause
The issue was caused by a conflicting MSBuild configuration where:
<DebugType>embedded</DebugType>embeds debug symbols directly into the main assembly<IncludeSymbols>true</IncludeSymbols>and<SymbolPackageFormat>snupkg</SymbolPackageFormat>attempt to create a separate symbol packageSolution
<DebugType>embedded</DebugType>setting to allow proper symbol package generationIncludeSymbolsandSymbolPackageFormat) to maintain debugging supportVerification
✅ Local testing confirms:
dotnet build -c Release- succeedsdotnet test -c Release -f net8- all tests passdotnet pack -c Release --include-symbols- both .nupkg and .snupkg created successfullyThe fix aligns with other successful repositories in the linksplatform organization that use the same symbol packaging configuration without the conflicting DebugType setting.
Test plan
🤖 Generated with Claude Code
Resolves #142