During a lunchtime discussion an interesting scenario came up. What if I already am working on a project that references log4net, since so many projects do, how do I take advantage of NuGet when a new version of Log4Net comes out?
Now this may be a bad example because they never seem to release new versions, but bear with me. :)
I'm not sure if this would be a feature of NuGet itself or it could be a package that adds a new command. But the basic idea is this.
Although packages are not 1-1 with assemblies, in many cases they are. So imagine if you could run a command that would look at all your assembly references and suggest packages to replace them with? Ideally, we'd implement a service on the NuGet.org side
that would maintain an index of package contents to package id. That way, you could send our server a list of assemblies and versions, and we'd send back package IDs that contain those assemblies, if any.
The goal would be to make it easy to upgrade a site from one that has plain old assembly references to one that is using NuGet to maintain dependencies. Thoughts?