There is a configuration option provided in Nu Get.config to disable source control integration and it is documented here: https://docs.nuget.org/Consume/package-restore/team-build However, I agree that we need a more user-friendly and discoverable way to enable this behavior wrote: Repro steps: - In Visual Studio 2013, create a new solution with a class library project. - Nu Get should not automatically add the contents of the "packages" folder to source control (for the reasons why, see the introductory text in this article about Package Restore from the Nu Get docs ).
Expected: - Only the project/solution files along with the "packages.config" file should be added to source control.
- Nu Get should offer a user-configurable option controlling this behaviour.
- In the Visual Studio options there is no option to prevent those unwanted pending changes.
— Reply to this email directly or view it on Git Hub @csharpfritz after the last repro step there is no "Nu Get.config" in my solution directory.
And -- to be blunt -- I dont want to create one either.
I want to use "Automatic Package Restore" which is supposed to give me the following advantages: @yishaigalatzer, I consider it broken, because the standard behaviour contradicts the Nu Get documentation.
Agreed, adding binaries to source-control for DEV branches is a bad practice.
Adding binaries to a master or production quality branch I consider a very good practice so that you always have all dependencies ready to deploy from a clean production instance of code..
That aside, adding binaries to source control is simply bad practice. The reason it is done this way is that we unfortunately cannot auto opt you into downloading packages. I do understand you dislike it, but any default we choose will break someone's flow. Its about behaviour the documentation implies, but Nu Get doesn't exhibit.
That aside, adding binaries to source control is simply bad practice.
Nu Get may offer to opt in for source-controlled libraries, but it shouldn't force the user to resort to work-arounds with outdated configuration switches (using nuget.config is the pre 2.7 way of package restore) in order to keep a bunch of binary files out of the repo.