is Paket supposed to respect the default dll path for nuget dependencies?
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
When installing a nuget dependency that has a dll in the root of the lib folder as well as a .NET 3.5 targeted version of the dll in a NET35 folder, Paket seems to always use the dll in the NET35 folder. It has the same behavior when no framework version is specified or when framework: >= net40 is specified in the paket.references file.
Repro steps
- Have a nuget with a default .dll in the lib folder and a dll in a NET35 subdirectory.
- Have the nuget dependency listed in the paket.dependencies file.
- Have the dependency listed in a paket.references file for a project.
- Run
paket.exe install
Expected behavior
The project file should reference the default dll in the nuget.
Actual behavior
The project file references the dll in the NET35 folder.
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 issue with paket.exe install using the described paket.dependencies and paket.references setup. Trace how the dependency's project-file reference is selected between the root lib DLL and the NET35 DLL. Done means the project file references the default root DLL when no framework or >= net40 is specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100