KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
Suppose you have Project A, and this has various dll dependencies, but the tree looks something like this: Project A => Project B => Project C => Project D => Project C => Project E => Project C, v2 Is there a way to use Project E since it relies on a newer version of Project C (dll) even though the rest of the project is using an older version of that same library? If there is not a way, or one that would cause much gnashing of teeth, is there a forward thinking solution to preventing this from happening on future projects?
Tags (comma-separated)
Save Edits
Cancel