This project is read-only.


Add support for versioning based on the versions of other installed packages


If a package creator wants to install different assemblies based on, say, the version of Razor used by a project, or of Entity Framework, she wouldn't have a good solution today, short of writing custom code to interrogate file versions is a powershell script, to do so.

See the post at for a concrete example of the problem.

We should provide a mechanism -- perhaps expanding our notion of a framework version in our folder structure -- to support this scenario.
Closed Jan 15, 2013 at 10:38 PM by
We commented on the discussion thread with a current solution for this problem. Adding logic into the lib folder structure would get far too complicated and NuGet needs to keep its dependency trees tracked by package dependencies.