| * reduced churn on proj files ensure consistency of dependencies across repository (can't do that with so many packages.config files) * easy to figure out outdated dependencies / update those with changes that are very easy to diff * no need to battle with transitive dependencies * several transitive dependencies resolution algorithm (max can be used to be as up-to-date as possible) * ease support for multi platform targeting (it puts conditionals around the references, when you switch platform, it switches to correct assemblies without you having to do anything) * will write/maintain binding redirects related to nuget packages for you (saves from many runtime errors) * can generate include scripts for nuget packages if you do .csx or .fsx scripting * many more things the UI integration in VS is not as good but if you look at it, the UI is also part of the problem with Nuget (doesn't work on several solutions, doesn't really understand transitive dependencies, etc.). You can migrate with single command line, and start improving from then on. |