Dependencies not downloaded initially

[Mystere]

I opened a different issue, but it turned out to be a red herring. It's a different problem altogether. I'm not sure why this is happening, and can't seem to track it down.

The problem is that if you install NuGetPowerTools from nuget package, the .nuget folder is created upon package install. This causes a problem when you Enable-PackageBuild because the .nuget folder already exists (but doesn't contain the dependent files like nuget.exe), so Ensure-NuGetBuild does not download the Nuget.Build (and consequently, the dependent Nuget.CommandLine).

If you delete the .nuget folder, then it will correctly re-create it, and download the dependencies. But because the .nuget folder is created on package install, this causes building to fail after the package is installed.

I can't figure out why the .nuget folder is being created on package install. The only weirdnss is that there's a packages.config file created inside the .nuget folder that has NuGetPowerTools listed in it. It's like installing the package causes the packages.config file to be installed into the .nuget folder. I can't seem to figure out where or how this might occur.

[davidfowl]

Give me some clear steps to repro the problem.

[Mystere]

1. Create a new Solution with project type ClassLibrary
2. Either via GUI or Command line, type in "Install-Package NuGetPowerTools"
3. Notice that .nuget folder is created in solution folder. Also, a Solution Item is added to the solution and contains a packages.config file
4. Enable-PackageBuild
5. Notice error "Failed to add import 'NuGet.targets' to ClassLibrary1"
6. Try to build project, fails with The imported project "ClassLibrary1.nuget\NuGet.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
7. Delete .nuget folder
8. Enable-PackageBuild
9. Everything builds.

Using NuGet 1.7, VS10 SP1, Windows 7 SP1 (and Server 2008 R2 SP1)

FYI, i've tested this on three different computers, same results. I even disabled all extensions to make sure there wasn't some extension interfering (such as Resharper) but that did not solve the problem.

[Mystere]

Are you able to repro the problem?

[davidfowl]

Didn't have time to repro it yet, thanks for the steps. Will try to get to it this week.

[Mystere]

Any movement on this?

[duleTitoAndolini]

I'm facing the same problems. Any solution?
Did you (Mystere) maybe found solution in the meantime?

[Mystere]

Well, the simple workaround is just to do as I say above. After you install Nuget-powertools, delete the .nuget folder, then type enable-packagebuild, then rebuild. It's annoying, but it works. It's kind of a problem when new users have to get the tree and build though.

I believe another option may be to enable Nuget package restore before you install Nuget-powertools. But I have not yet tried it.

[duleTitoAndolini]

Thank you very much, it works.