Dotnet restore does not honour nuget.config 'repositoryPath'

Steps to reproduce

1. dotnet new in an empty directory
2. Add the following nuget.config to the same directory

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <config>
        <add key="repositoryPath" value="c:\packages" />
    </config>
    <packageSources>
        <clear />
        <add key="NuGet" value="https://api.nuget.org/v3/index.json" />
    </packageSources>
</configuration>

1. dotnet restore in the same directory

Expected behavior

Packages for the solution are restored to c:\packages

Actual behavior

Packages for the solution are restored to c:\users<username>.nuget\packages

Environment data

.NET Command Line Tools (1.0.0-preview1-002702)

Product Information: Version: 1.0.0-preview1-002702 Commit Sha: 6cde21225e

Runtime Environment: OS Name: Windows OS Version: 6.3.9600 OS Platform: Windows RID: win81-x64

Additional

I understand that the packages path can be passed as an argument to the dotnet restore command, however this only works at the CLI level, what happens when Visual Studio does a restore? Previously, the packages path could be provided in the global.json (for DNX/RC1 ASP.NET projects) but this also no longer works.

[Kieranties]

@emgarten Thank you, I think that clears up the issue.

To confirm, creating a config as follows

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <config>
        <add key="globalPackagesFolder" value="c:\packages" />
    </config>
    <packageSources>
        <clear />
        <add key="NuGet" value="https://api.nuget.org/v3/index.json" />
    </packageSources>
</configuration>

and performing dotnet restore at the root of a solution restores packages to c:\packages

I can also confirm that performing restore in Visual Studio also recognised the configuration and restored to the configured path.

---

Question: Setting the value to simply packages (or any relative path) creates a packages folder relative to the project.json for each project in a solution that is restored. Is that expected behaviour?

[vcsjones]

I think dotnet and nuget in general prefer using the NUGET_PACKAGES environment variable now.