Paket does not add all project references for some NuGet packages
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
When I install the Prius NuGet package Paket only adds one project reference even though the NuGet package defines two references.
You can see from this nuspec file that Prius needs 2 project references to be added Prius.Contracts.dll and Prius.ORM.dll but when I add this NuGet package to my project Paket only adds a reference to Prius.Contracts.dll
Repro steps
- Start a new console app in Visual Studio 2013
- Configure Paket and add a reference to the
PriusNuGet package. - Run
paket install - Examine the project references and see that
Prius.ORM.dllis not referenced - If you write code that uses Prius then the application will fail at startup because
Prius.ORM.dllis missing from the bin folder.
Expected behavior
Paket should examine the <references> section of the nuspec file and include all of the references listed there.
Actual behavior
Paket only creates a project reference for the first <reference> listed in this case. I did not find any other examples to see if it is always just the first one that is referenced.
Known workarounds
You can manually add the missing reference to the project
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 by reproducing the issue with the Prius NuGet package and trace Paket's handling of the nuspec section. Verify how project references are created when multiple DLLs are listed. Done means both Prius.Contracts.dll and Prius.ORM.dll are added to the project and the application includes Prius.ORM.dll in its bin folder.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100