-
Notifications
You must be signed in to change notification settings - Fork 51
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
Cannot locate .paket folder #152
Comments
Hi, I've got 0.37.7 installed but am still seeing the above issue. |
@forki can you re-open this please, i am also still seeing this issue :( Restoring packages the .paket folder is under the MyRepo folder |
Please send a pull request |
i can try ;) |
Thanks
Am 20.10.2017 17:21 schrieb "Chris Blyth" <[email protected]>:
… i can try ;)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#152 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADgNBq_j6ix0kBBQRUaQl0n1muqfTZ_ks5suLpwgaJpZM4P7vhV>
.
|
Tested and this and it now works! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Since recent update i get build error saying restore failed as the .paket folder cannot be located.
It it looking 1 level too deep for the .paket folder.
Repro steps
Setup repo as follows:
| .paket
|->| paket.exe
|->| paket.bootstrapper.exe
| src
|->| MyProject
|->|->| MyProject.csproj
|->|->| MyProject.sln
|->| MyOtherProject
|->|->| MyOtherProject.csproj
|->|->| MyOtherProject.sln
|->| MyCombinedSolution.sln
When building from any of the 3 solutions it searches for the .paket folder under the src folder and not at the root of the repo.
Expected behavior
Paket is found and used
Actual behavior
packet is not found and errors
Known workarounds
put the .paket folder under the src folder
Related information
The getting started (https://fsprojects.github.io/Paket/getting-started.html) states to create at the root.
The text was updated successfully, but these errors were encountered: