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.
No way to include text files in package using dotnet pack command
See original GitHub issueSteps to reproduce
put the following text in project.json:
“buildOptions”: { “copyToOutput”: [ “MyOwnTextFile.config” ] },
run dotnet pack
Expected behavior
nupkg contains “MyOwnTextFile.config” file
Actual behavior
nupkg does not contain “MyOwnTextFile.config” file
Environment data
dotnet --info output:
.NET Command Line Tools (1.0.0-preview2-003121)
Product Information: Version: 1.0.0-preview2-003121 Commit SHA-1 hash: 1e9d529bc5
Runtime Environment: OS Name: Windows OS Version: 6.1.7601 OS Platform: Windows RID: win7-x64
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Nice! Now it has correct place in package.
But how to tell that this file should be placed in project and copied on build to output?
In other words setup “contentFiles”:
https://docs.nuget.org/create/nuspec-reference#contentfiles-with-visual-studio-2015-update-1-and-later
You should use
packOptions, notbuildOptions.