Is it necessary to keep folders in the C# project in the git repository of the project?

[esther]

I have two projects. HelloWorld and HelloWorld.UnitTests♪ Second application nuget I did. NUnitwhich created a folder packages♪ Using Visual Studio 2013.

Now the repository looks like:

.\HelloWorld\
.\HelloWorld.UnitTests\
.\HelloWorld.UnitTests\packages.config
.\packages\
.\HelloWorld.sln

Daddy. packages came after an active project. HelloWorld.UnitTests and used the team. Install-Package NUget in the consoles.

In Python, there are so-called addiction files and you can use a team. pip install -r requirements.txt♪ But there's no such decision in C#. I'm embarrassed that I'm gonna have to keep a lot of dll files, even though it would be more logical for the repository to keep a file of relationships similar to a python-ow decision with a python-ow decision. requirements.txt A file.

Do I understand correctly that I will have to keep this folder in the project repository?

[Marcee]

The main method of connecting/reliance on the project is nuget. You should have a packages file in the project file.config. It stores data on the nuget-packets used in the project. Adding VCS needs it. The necessary packages will be downloaded on the basis of the data contained therein. Dll'ka don't need to be included. Example: