Paket pack does not include project those are added as reference.
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
I have created a visual studio C# solution which contains two projectA and projectB. Both project have its own paket.template file.
projectB is added as a reference in projectA (means as an assembly reference in Visual Studio files. NOT as in paket.references.)
In both paket.template files --include-referenced-projects true is given.
- observed behavior : There is no dependency of projectB, in nuget package of projectA.
Expected behavior
-Expected behavior : When nuget package for projectA is created it must contains projectB as <dependency ...... /> attribute.
Known workarounds
- If projectB assembly name is added in paket.template under dependencies section, the nuget package of projectA does contains projectB as a dependency attribute.
What all I try
I tried using paket.pack command with attribute --include-referenced-projects, but still package that was created does not contains projectB dependency.
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
Reproduce the package creation described with two C# projects, separate paket.template files, and projectB as an assembly reference rather than a paket reference. Start by tracing how paket pack handles --include-referenced-projects and compare the generated package for projectA with the expected projectB dependency; done means the dependency is emitted without manually adding it to the dependencies section.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100