Do you work on Solutions with multiple projects but a single main application (or even with multiple apps, but all in support of the single main application?)
Do you work on solutions with multiple distinct applications?
Would you prefer to always have the same version of an assembly across every project in the solution? Thus if you install Log4Net 1.1 in one project, but you had Log4Net 1.0 in another project within the same solution, you’d want the older version automatically upgraded to log4Net 1.1?
Do you have solutions where two different projects use different versions of the same assembly? This might happen if you add a reference to a library in one project, and then later add a newer version of the same assembly to another project without also updating the first project with that newer version
Are you in a situation today where you absolutely need different versions of the same assembly within a single solution.
Finally, if you’re using NuGet today, please look at the packages folder in the root of your project. How many packages have multiple versions?