-
Notifications
You must be signed in to change notification settings - Fork 258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PackageReference - Should Project File be autosaved after nuget operations #6013
Comments
@bradphelan what kind of project are you encountering this with? |
its a large project. about 30 sub projects. most are new SDK type projects
targetting net461 and there are two fsharp projects in there. might be one
old style csproj file but i am sure i converted everything.
…On Thu, 12 Oct 2017, 01:53 Rohit Agrawal ***@***.***> wrote:
@bradphelan <https://github.com/bradphelan> what kind of project are you
encountering this with?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6013 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AABE8rAkqOqj_o0AbBwDEl4TqykyEoHaks5srVUEgaJpZM4P07nY>
.
|
I can confirm the original bug report (project files are not saved after nuget update) and also the UI glitch for Consolidate tab. Please fix these. |
@donnie-msft and i were walking through the scenario matrix...not done yet: add a new class add ref to binary installing package uninstalling package upgrading package related? #7241 |
Triage: We should verify whether this is still happening. |
Details about Problem
I selected a nuget package to update. After it is finished the UI still says the package is at the old version. I look on the filesystem and the PackageReferences are still at the old version. I then click save all and all the project files are updated.
I assume that the system forgets to do a save all after doing the nuget update.
The text was updated successfully, but these errors were encountered: