Failed to regenerate a new cache file after deleting cache file and rebuilding solution #13451
Labels
Found:ManualTests
Functionality:Restore
Priority:1
High priority issues that must be resolved in the current sprint.
RegressionDuringThisVersion
A regression which broke since last RTM, and was fixed before the next RTM.
Type:Bug
Milestone
NuGet Product Used
Visual Studio Package Management UI
Product Version
NuGet Client Dev\6.11.0.55
Worked before?
It is a regression since it doesn’t repro on Main\34915.142 + NuGet Client Dev\6.11.0.50.
Impact
It's more difficult to complete my work
Repro Steps & Context
Repro Steps:
Create a C# Console App (.NET Core) project in VS.
Build the solution, observe generate a restore cache file inside obj/ folder.
Delete the cache file manually.
Rebuild the solution, observe if it will regenerate a cache file inside obj/ folder and the timestamp is updated.
Expected:
A cache file with an updated timestamp is regenerated in the obj/ folder.
Actual:
No cache file is regenerated in the obj/ folder as below:
![time](https://private-user-images.githubusercontent.com/84695155/332013231-374a87ec-6ff0-4619-87af-86825ca0a120.gif?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ1MDgyMzcsIm5iZiI6MTcyNDUwNzkzNywicGF0aCI6Ii84NDY5NTE1NS8zMzIwMTMyMzEtMzc0YTg3ZWMtNmZmMC00NjE5LTg3YWYtODY4MjVjYTBhMTIwLmdpZj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODI0VDEzNTg1N1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBhYWFjNjA3YTRlOTBjNjk2ODE5NTI1MzgwYzAzM2QyOGI2ZDAzYTBhODM3YTgzMWUxNjk0MzI4YzEwZDk4MDcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.7THSxRtovuZmYRDK3yNlhtcmY812r3IMGdYWlMWLpJ0)
Notes:
The repro rate is 100%.
It also reproes on UWP project and non-SDK project that install package with “PackageReference” format
Verbose Logs
No response
The text was updated successfully, but these errors were encountered: