When adding a solution to TFS source control using the built-in "Add Solution to Source Control" gesture, NuGet adds the 'packages' folder to the list of pending changes. However, when doing this with the new built-in "Git" option in VS 2013, the packages folder is missing, leaving users unable to build the solution when they check it out.
Repro steps for VS 2013:
1. Create a new C# project (Note: Do not enable Package Restore)
2. Add a Package to the project (I suggest 'FourOne.Memes')
3. Right click the solution and select "Add Solution to Source Control"
4. Select Git
Expected: The "packages" folder appears in the "Included Changes" list in the "Team Explorer > Changes" tool window.
Actual: The "packages" folder appears in the "Untracked Changes" list in the "Team Explorer > Changes" tool window.
This makes it easy to push the files without the "packages" folder and move to another machine to find that it doesn't build.
Repro steps for VS 2013:
1. Create a new C# project (Note: Do not enable Package Restore)
2. Add a Package to the project (I suggest 'FourOne.Memes')
3. Right click the solution and select "Add Solution to Source Control"
4. Select Git
Expected: The "packages" folder appears in the "Included Changes" list in the "Team Explorer > Changes" tool window.
Actual: The "packages" folder appears in the "Untracked Changes" list in the "Team Explorer > Changes" tool window.
This makes it easy to push the files without the "packages" folder and move to another machine to find that it doesn't build.