Net471 project: Paket pulls in netstandard2.0 dependency instead of net35
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 repro here
Basically it's a Framework v4.7.1 project pulling in 2 dependencies: xUnit and Jetbrains DotMemory
DotMemory has 2 libs: netstandard2.0 and net35
Paket is pulling in the netstandard2.0 library (see the .csproj file), whereas I would have expected it to pull in the net35 dependency.
How can I trace why Paket is choosing that library, and how can I force it to choose the net35 library instead?
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 linked dotmemoryrepro repository, especially ClassLibrary1/ClassLibrary1.csproj around line 72, and compare the package's lib/netstandard2.0 and lib/net35 assets. Trace Paket's framework and dependency selection for this repro. Done means the cause is identified and the repro either selects net35 for the .NET Framework project or documents a supported way to force that asset.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100