-
Notifications
You must be signed in to change notification settings - Fork 694
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
Updates PowerShell scripts #4006
Conversation
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 for fixing our build script.
I have 1 comment.
@@ -70,15 +70,17 @@ | |||
However, our MSBuild integration tests use Microsoft.Build 16.8.0, which requires System.Threading.Tasks.Dataflow 4.9.0 (assembly version 4.9.3.0). | |||
To resolve runtime assembly binding failures, we'll downgrade the package from 4.11.1 to 4.9.0. | |||
--> | |||
<PackageReference Update="Microsoft.VisualStudio.VCProjectEngine" Version="16.9.31025.104" /> |
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.
By removing condition for VS15, is build script stop supporting VS15?
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.
In theory, yes. I tested building for VS15 with this change, and, it didn't work. Failures indicate a .NET Core SDK issue
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.
If I leave the VS15 condition, it could work, but, we still need to address the .NET Core SDK Issue
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.
We depend on changes to CPS & the .NET project system that are available only in d16. I think we're a long time past "not supporting" d15 from our dev branch. Our build scripts just haven't kept up.
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.
It's potentially a change with some tail, but we should change our output location to VS
only or something else.
VS15
referred to dev15. When we moved to dev16, we didn't change it because we didn't want to chase the tail.
I think we have an opportunity to change it now.
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.
So then do we need 15
in [ValidateSet(15, 16, 17)]
now?
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.
Since the script does not build for dev15, I will remove 15
in the set.
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.
LGTM.
c76ad61
to
cf5424c
Compare
This reverts commit cf5424c82036cd298bfcb5782d0d0c52cbb44fe5.
0ad1ddb
to
951706d
Compare
Bug
Fixes: https://github.com/NuGet/Client.Engineering/issues/903
Regression? No Last working version:
Description
.\artifacts\configure.json
PR Checklist
PR has a meaningful title
PR has a linked issue.
Described changes
Tests
[ ] Automated tests added[ ] Test exceptionDocumentation
[ ] Documentation PR or issue filled