"paket restore" fails if a dotnet project is open in Visual Studio
Open
Nobody has claimed this yet.
extern
sdk: dotnet/sdk
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
paket.exe restore fails if a .NET Core / .NET Standard project is open in Visual Studio 2017.
Repro steps
- Create a .NET Core or .NET Standard project.
- Manually import
Paket.Restore.targets - Set up
paket.dependenciesandpaket.lock - From a command prompt, run
paket.exe restore - Open the project in Visual Studio
- From a command prompt, run
paket.exe restoreagain
Expected behavior
Package restore process succeeds.
Actual behavior
Checking Paket version (version 5.130.6 requested)...
Paket.exe 5.130.6 is up to date.
Paket version 5.130.6
Performance:
- Runtime: 1 second
Paket failed with
-> UnauthorizedAccessException: Access to the path 'C:\Path\To\Project\obj\Project.csproj.paket.references.cached' is denied.
Known workarounds
Close Visual Studio before running paket restore
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 five-step scenario with a .NET Core or .NET Standard project while Visual Studio is open, focusing on the denied obj\Project.csproj.paket.references.cached path. Trace the restore operation that accesses this cache file and compare behavior with Visual Studio closed. Done means paket.exe restore succeeds while the project remains open.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100