Package version number for build packages

Topics: General
Dec 2, 2013 at 2:39 PM
As part of building a package, NuGet stamps packages with an internal version number that determines the minimum version of the NuGet client the package is compatible with. This lets the client tell the user they are using an out-of-date version.

I noticed that when I was installing a package with the "build" folder on an old client, no message popped up and NuGet silently ignored adding the targets file. This probably means we decided not to rev the package version when we added support for this feature. Was this intentional?