I have a project(s) that I’m writing NUnit tests for (for example). I want to commit the code to git, but I also feel it’s bad practice to commit the NuGet packages (NUnit and NUnit.Runner) to the repo. However, I don’t want to also turn on Package restore either since I believe it’s a user setting and not a project setting (IIRC).
What is the right way to add .NET project with NuGet dependencies to a git repo? I assume it would be something that would happily grab the Packages but one that requires developer intervention. Perhaps just expect other developers to know to add those missing packages back into the project? (It also seems like we’d end up resolving .csproj conflicts all the time too).
If unable or unwilling to enable package restore, a developer can easily add all packages by command line, as explained in this question:
You can also run this in a pre-build command, as explained here:
But really, package restore is easier, it merely requires a few clicks.