New Post: Removing the version parameter from the packages.config file does not work

dotnetjunky wrote:

kingikra wrote:

Now let's say there's a certain initial version number for this parameter and whenever a newer package is being installed, the value of this parameter will be changed to the new version number. If one developer has updated this package two days ago, and another developer is updating this package today to a newer version than the other developer, commiting will cause a conflict. It is a never ending story.

How is it different than any file belonging to source control? The second developer will just need to solve conflict and pick his version before checking in.

The preferred way to work with packages.config files is NOT to touch it at all. Let NuGet manage it on its own.

First of all thanks for the fast response.
What I did not understand is your last sentence. If I won't touch it at all, at one point, the version of a package will be so old that it'll not be present in the NuGet server.
(We cannot leave all packages in the NuGet server as it'll grow in size to be a monster).

Thanks
Gil