copy_local: true has no effect on netstandard projects
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
Dependencies are not copied to the output directory of a project targeting netstandard2.x (but they are for net4x).
Repro steps
Please provide the steps required to reproduce the problem
-
dotnet new -i "MiniScaffold::*" -
dotnet new mini-scaffold -
After restore/build completes, check
{proj}\bin\Debug\net461and see dependencies copied. Check{proj}\bin\Debug\netstandard2.1and see no dependencies copied.
If possible then please create a git repository with a repro sample or attach a zip to the issue.
Expected behavior
Expect copy local behavior to match paket directive. This is rather important for building certain things, like type providers. I also think this is the root cause of BenchmarkDotNet#1392.
Actual behavior
The paket directive seems to not matter. See also: #3645, #3352, #3154, #3186.
Known workarounds
None? Using PackageReference instead of paket, I guess
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the MiniScaffold reproduction and compare the built net461 and netstandard2.1 output directories after restore/build. Review the copy_local behavior and the related issues #3645, #3352, #3154, and #3186; done means dependencies are copied for netstandard2.x as they are for net4x.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100