Skip to content
This repository was archived by the owner on Dec 18, 2017. It is now read-only.

NuGetDependencyResolver should take precedence over all except ProjectResolver #549

Closed
davidfowl opened this issue Aug 19, 2014 · 1 comment
Closed

NuGetDependencyResolver should take precedence over all except ProjectResolver #549

davidfowl opened this issue Aug 19, 2014 · 1 comment
Assignees
@davidfowl
Labels
3 - Done bug
Milestone
1.0.0-beta1

Comments

@davidfowl
Copy link
Member

Today the NuGetDependencyResolver comes after the GacDependencyResolver and ReferenceAssemblyDependencyResolver. This causes issues when there's an assembly in the GAC that has the same version as a NuGet package being referenced. Unfortunately the same is also true for reference assemblies that are exists as NuGet packages.

We should only consider the NuGet package valid if there are any compilation exports for that targetFramework (i.e. if there's a compatible lib folder for that target framework).

Related to #506
@davidfowl davidfowl added this to the 1.0.0-alpha4 milestone Aug 19, 2014
@davidfowl davidfowl self-assigned this Aug 19, 2014
@davidfowl davidfowl modified the milestones: 1.0.0-beta1, 1.0.0-alpha4 Sep 3, 2014
@davidfowl
Copy link
Member Author

This was resolved with #640

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@davidfowl davidfowl

Labels
3 - Done bug
Projects
None yet
Milestone
1.0.0-beta1
Development

No branches or pull requests
1 participant
@davidfowl