-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Fix setting package versions in VS insertion #11094
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
Conversation
JanKrivanek
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
|
/backport to vs17.12 |
|
Started backporting to vs17.12: https://github.com/dotnet/msbuild/actions/runs/12198365503 |
|
/backport to vs17.11 |
|
Started backporting to vs17.11: https://github.com/dotnet/msbuild/actions/runs/12198377051 |
|
/backport to vs17.8 |
|
Started backporting to vs17.8: https://github.com/dotnet/msbuild/actions/runs/12198379379 |
|
vs17.10 was not merged so let's put it in the PR directly |
Fixes #11092
Context
a "refactor" in prior VS insertion pipeline PR introduced a bug where package properties would be set to empty string resulting in no update of them in VS PR
Changes Made
fix setting properties in the embedded PowerShell
Testing
(internal) https://devdiv.visualstudio.com/DevDiv/_git/VS/pullrequest/596781?_a=files
(internal) https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=10665100&view=results
Notes
to be backported to vs17.8,10,11,12