Getting error "FileNotFoundException: Could not find file '..\script\paket.dependencies". want to keep all my dependence in root folder only.
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
Want to keep all my dependence (package folder) in root folder only. used paket.references to achieve, but getting **FileNotFoundException: Could not find file '..\script\paket.dependencies** error.
Repro steps
I have folder structure as specified below.
src
--> script
--> build.fsx
--> fake.cmd
--> paket.references
--> svc
--> packages
--> paket.dependencies
the script folder will have F# Make script. in that i have refer my group packet. the code snap given below
#r "paket: groupref build //"
My paket.references will look like this
// [ FAKE GROUP ]
group Build
source https://api.nuget.org/v3/index.json
nuget Fake.Core.Target
when i try to run my script getting below error
There was a problem while setting up the environment:
-> FileNotFoundException: Could not find file '..\script\paket.dependencies'.
Expected behavior
All my dependence should be in root folder only (package folder). the script should run with all it dependence .
Actual behavior
Getting FileNotFoundException: Could not find file '..\script\paket.dependencies error.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the setup using src/script/build.fsx, fake.cmd, paket.references, the root packages folder, and root paket.dependencies, then run the script to confirm the path failure. Trace how the script locates paket.dependencies and make the expected root-level dependency layout work without the FileNotFoundException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100