Latest drop of nuget extension is ignoring already installed packages for the solution/projects

And I already have automapper installed in other projects for this solution. Nuget in it's smartness is just ignoring that fact and installing the latest version on this project. This could affect multiple versions back, I just haven't done this in awhile.

Expected behavior (and how it's worked in the past):

Reference the existing package, and perform other install operations against the project on that existing package. Don't try to go get a new one.

I wasn't aware that NuGet didn't try to get the latest version in the past. If it behaved that way, maybe it was accidental. I know our intention is always to install the latest version if you don't explicitly set the -Version parameter.

So what you are saying is that IF I already have AutoMapper v 2.0.0 installed in OTHER projects in the solution, you are going to install 2.1.0 into a newly added project to the solution instead of using the already installed v 2.0.0? This doesn't try
to upgrade already installed version on the other projects so this would effectively create multiple versions of AutoMapper against one solution. This behavior was was fixed back in v1.4 because it was bad...

It was working, that's the thing. And if you ask a group of people how they would like it to work when they install the same package in several projects under the same solution, they will want it to be the same version they installed in the first project
unless they specifically ask for a different version, or attempt to install something that requires a different version.

This is such a slam dunk from a usability standpoint I don't get what the hesitation is. Perhaps it is that I'm not really explaining it correctly?