Skip to content
This repository has been archived by the owner on Oct 2, 2019. It is now read-only.

Framework specific dependencies don't consider indirect dependencies #2

Open
terrajobst opened this issue Aug 25, 2014 · 0 comments
Open
Assignees

Comments

@terrajobst
Copy link
Member

Ported from CodePlex

Repro:

  1. NuProj references two projects: PortableLib and DesktopLib
  2. PortableLib is portable, DesktopLib is .NET 4.5.1
  3. DesktopLib depends on PortableLib
  4. PortableLib references a NuGet package, DesktopLib doesn’t

Actual Behavior:

NuGet dependency is only added to portable, but not for .NET 4.5.1

Expected Behavior:

DesktopLib also depends on PortableLib, which is why it should also be referenced from portable

@terrajobst terrajobst added the bug label Aug 25, 2014
AArnott pushed a commit to AArnott/nuproj that referenced this issue Sep 29, 2014
@terrajobst terrajobst assigned terrajobst and unassigned terrajobst Oct 22, 2014
@terrajobst terrajobst self-assigned this Jan 12, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant