Closed omatrot closed 6 years ago
I have the same issue: we put the packages at the root of our branches in a special folder named 'ThirdParties' and not 'packages' but it looks for 'packages'.
@loicmorvan I'm temporarily using a directory symbolic link to solve the problem.
@omatrot For now, I can just use the version "v2.2.0-xbuild02" which works well waiting for a new update.
Issue still alive in v2.3.0
I just created PR #38, which addresses this issue.
@omatrot @loicmorvan @DuAell @shauser see issue #39
PR merged
This works only we you case the config parameter name correctly.
In the sample I've given above, repositorypath
is lower case. It still fails.
It works with an uppercase P for path: repositoryPath
.
Using the latest prerelease version of the nuget in both VS 2015 & VS 2017 I have the following error during compilation.
CUSTOM_PATH & blablabla above are obfuscation of real paths.
Please note that we're sharing packages at the root of our TFS branch. The task seems to look for packages in the solution folder.
We do have a repositoryPath configured in a nuget.config at solution level:
<add key="repositorypath" value="$\..\..\..\..\..\packages" />
.csproj included. csproj.zip