Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The "PackageRetrievalTask" task failed unexpectedly #33

Closed
omatrot opened this issue Mar 22, 2017 · 8 comments
Closed

The "PackageRetrievalTask" task failed unexpectedly #33

omatrot opened this issue Mar 22, 2017 · 8 comments

Comments

@omatrot
Copy link

omatrot commented Mar 22, 2017

Using the latest prerelease version of the nuget in both VS 2015 & VS 2017 I have the following error during compilation.

The "PackageRetrievalTask" task failed unexpectedly.
1>D:\CUSTOM_PATH\packages\Baseclass.Contrib.Nuget.Output.2.3.0-vs20172\build\net40\Baseclass.Contrib.Nuget.Output.targets(65,5): error MSB4018: System.IO.DirectoryNotFoundException: Could not find a part of the path blablabla\packages'.

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

@loicmorvan
Copy link

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'.

@omatrot
Copy link
Author

omatrot commented Mar 29, 2017

@loicmorvan I'm temporarily using a directory symbolic link to solve the problem.

@loicmorvan
Copy link

loicmorvan commented Mar 29, 2017

@omatrot For now, I can just use the version "v2.2.0-xbuild02" which works well waiting for a new update.

@DuAell
Copy link

DuAell commented May 9, 2017

Issue still alive in v2.3.0

@shauser
Copy link

shauser commented Aug 2, 2017

I just created PR #38, which addresses this issue.

@fabiosalvi
Copy link

@omatrot @loicmorvan @DuAell @shauser see issue #39

@romerod
Copy link
Member

romerod commented Nov 10, 2017

PR merged

@romerod romerod closed this as completed Nov 10, 2017
@omatrot
Copy link
Author

omatrot commented Nov 12, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants