1.0.4 CLI fails to create prime cache if 2.0.0-preview1-005972 version is installed as well
See original GitHub issueSteps to reproduce
- Install CLI version
1.0.4
- Install CLI version
2.0.0-preview1-005972
- Create a new project that targets
netcoreapp1.0
- Add a global.json with contents
{ "sdk": {"version": "1.0.4"} }
- Run
dotnet restore
Expected behavior
The first time experience behavior completes and prime cache is created successfully for version 1.0.4
Actual behavior
Failed to create prime the NuGet cache. new failed with: -2147352571
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Failed to create prime the NuGet cache. new failed with: 5
A command is running to initially populate your local package cache, to improve restore speed and enable offline access. This command will take ......
Read more >Failed to create prime the NuGet cache, dotnet restore.
I installed .net core 2.0; I changed package varsion to: 1.0.4 in .csproj; I used command dotnet nuget locals -c all and after...
Read more >Builds always fail until clearing cache and re-trying
But when I manually “clear cache and retry”, it builds just fine. It also runs just fine locally on various machines (windows/mac/linux). For ......
Read more >update-file-cache — AWS CLI 1.29.25 Command Reference
For more information see the AWS CLI version 2 installation instructions and ... Updates the configuration of an existing Amazon File Cache resource....
Read more >Using the Infinispan Command Line Interface
Infinispan cache instances. The default cache container is empty. Use the CLI to create caches from templates or infinispan.xml files. counters.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That feels like cheating. 😉
DOTNET_SKIP_FIRST_TIME_EXPERIENCE
does make the problem “go away” for now. Thanks!@livarcocc this happens when you use the 2.0.0-* versions for playing around and then using
1.0.4
again through aglobal.json
file (and nuking the nuget cache to trigger first run experience). I think the problem is that there is no public / “released” build of1.0.*
that contains dotnet/cli#6633 yet.