Consider this scenario: we target NET45 and nothing else. To indicate that fact we put "framework: net45" at the top of paket.dependencies, which in my understanding supposed to work the same as adding "framework: net45" to each package. Still we get this in the paket.lock:
ZendeskApi_v2 (3.0.2)
AsyncCTP - framework: >= net40
Package ZendeskApi_v2 depends on AsyncCTP ONLY for net40 and the fact that we get it for net45 actually causes build break, because AsyncCTP cannot be used with net45.
After vigorous pounding my head against the wall I found the workaround:
nuget ZendeskApi_v2 3.0.2 framework: >= net45
with that AsyncCTP does not get wired up to the project.
But WHY framework: >= net45 works better (or even differently) than framework: net45 is a mystery which keeps me awake at night. Could somebody please shed some light onto what is going on here?
Consider this scenario: we target NET45 and nothing else. To indicate that fact we put "framework: net45" at the top of paket.dependencies, which in my understanding supposed to work the same as adding "framework: net45" to each package. Still we get this in the paket.lock:
ZendeskApi_v2 (3.0.2)
AsyncCTP - framework: >= net40
Package ZendeskApi_v2 depends on AsyncCTP ONLY for net40 and the fact that we get it for net45 actually causes build break, because AsyncCTP cannot be used with net45.
After vigorous pounding my head against the wall I found the workaround:
nuget ZendeskApi_v2 3.0.2 framework: >= net45
with that AsyncCTP does not get wired up to the project.
But WHY framework: >= net45 works better (or even differently) than framework: net45 is a mystery which keeps me awake at night. Could somebody please shed some light onto what is going on here?