After paket clear-cache I cannot run paket anymore
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
Repro steps
I ran a dotnet paket clear-cache and trying to run paket again, I get:
Cannot use file stream for [C:\Users...nuget\packages\paket\6.2.1\tools\netcoreapp2.1\any\paket.deps.json]: No such file or directory
A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in 'C:\Users...nuget\packages\paket\6.2.1\tools\netcoreapp2.1\any'.
Failed to run as a self-contained app.
- The application was run as a self-contained app because 'C:\Users...nuget\packages\paket\6.2.1\tools\netcoreapp2.1\any\paket.runtimeconfig.json' was not found.
- If this should be a framework-dependent app, add the 'C:\Users...nuget\packages\paket\6.2.1\tools\netcoreapp2.1\any\paket.runtimeconfig.json' file and specify the appropriate framework.
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
Start at the dotnet paket clear-cache command entry point and reproduce the failure by running Paket again afterward. Inspect how the cache-clearing operation affects paket.deps.json, paket.runtimeconfig.json, and hostpolicy.dll under the NuGet package path. Done means clearing the cache no longer leaves Paket unable to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100