netcoreapp1.* shouldnt use packages with tfm > netstandard1.* (netstandard2.* is not valid)
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
It's more a question than bug. I can understand it if it by design, but is is quite annoying.
I'm trying to target .net core 1.1 but some resolved packages are .net core 2 only.
Repro steps
Use this paket.dependencies:
source https://www.nuget.org/api/v2
framework: netcoreapp1.1
storage: none
nuget Microsoft.Extensions.DependencyInjection
Expected behavior
Paket would help me by getting Microsoft.Extensions.DependencyInjection 1.1.2 which compatible with "netcoreapp1.1".
Actual behavior
It is referencing Microsoft.Extensions.DependencyInjection 2.0.0 which is "netcoreapp2.0" only.
Known workarounds
I can use "~> 1" of course, but it gets a little bit tedious if there are more assemblies like that.
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
Use the supplied paket.dependencies with framework netcoreapp1.1 and the Microsoft.Extensions.DependencyInjection dependency to reproduce the resolution. Compare the selected 2.0.0 package with the expected 1.1.2 compatibility rule; done means the resolver avoids netstandard2.* packages for netcoreapp1.* targets without requiring a manual ~> 1 constraint.
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
- 35/100