Packages directory

[dennismi]

Hi David

Nice work, have only one issue with it and that is...

We are using TFS and I have avoided checking in the packages folder, but every time i load the solution (with a deleted packages dir) it gets added once again. Any way of getting around that?

My reason for doing this is that i'm mimicking a fresh install (be it a new developer or a reinstall of some box)

Regards
Dennis

[davidfowl]

There's a super hacky way to do it (btw we plan to fix this in the next version) but it involves going to the nuget install directory and deleting the NuGet.TeamFoundationServer assembly.

[dennismi]

but what if the user doesn't have nuget installed, and just uses it from .nuget folder?

[dennismi]

and wouldn't that be the nuget VSIX install dir? in %PROGRAM FILES%\nuget there isn't any nuget.tfs assembly

[davidfowl]

Then it wouldn't get checked back in right? The .nuget folder has everything needed to restore packages. If developer A has nuget and installs some package foo and doesn't commit the packages folder, then developer b get's the latest and builds, nuget.exe will restore the packages (it's in the .nuget folder).

Btw everyone should gave nuget :)

[davidfowl]

The install directory is:
Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Microsoft Corporation\NuGet Package Manager\1.5.20831.9017

[dennismi]

My point is

if i remove(delete) the packages folder from the disk, and do a build it will get the packages, but it also does add the packages folder to TFS.

Could that actually be because i have both Nuget VSIX and NuGet CMD installed.

I must say i haven't noticed if this behaviour occurs on some of my team members pc's...

will have to get back to you on this

[davidfowl]

We always add the packages folder to tfs. Like I said before, the workaround (albeit hacky) is to delete the NuGet TFS assembly from your install (and your other devs install). In 1.6 we plan to make it so that this is configurable (probably off by default)

[dennismi]

I have the opinion that the less we need to install on the box the better, hence i prefer to manage the package from a single machine - and I don't actually trust my co-workers to remember NOT to checkin the packages folder :)

However, just talked to one of my team mates, and it does not add the folder when installing it via the .nuget/nuget.exe file.

this in turn highlights that when you got nuget installed (VSIX atleast) it will actually use that instance instead of the .nuget version. Or it loads support assemblies from the installation directory, which in my opinion is an unfortunate side-effect. It could be by design.

When the option arrives in 1.6, will you tool then be obsolete or just scaled down to just include the build targets?

[davidfowl]

When 1,6 comes out this will be reduced to package building and other helper functions