Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Rebuild Microsoft.CodeAnalysis #50968
Rebuild Microsoft.CodeAnalysis #50968
Changes from 9 commits
3cf2d73
3794254
d784e62
4fd9f08
fce5c72
2a5bbda
0b2b376
dbc5eba
3f395ac
85c2a78
642fa3b
c78add0
08b6278
cba4618
1452beb
0644bfb
fdcaf96
3a277d7
7275aad
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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'd be better to have this logic in a
eng/validate-rebuild.ps1
file, so it can be easily run locally.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.
Actually, why not call test-rebuild.ps1?
In reply to: 578014609 [](ancestors = 578014609)
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.
This change (and similar changes in other tests) were required due to the mdv version update.
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.
This is a temporary change correct? The idea being that when we are done with this effort that we will be adding this to
Directory.Build.props
? If so are we tracking that in an issue, comment, etc ...?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.
Filed #51099 to track. There is a bug in wpf temp projects that prevent us from enabling this in Settings.props or Directory.Build.props for now (is one or the other preferred? Directory.Build.props seemed pretty empty.)
I should probably file the bug to get this property fixed with WPF projects. Do you know the right repo to do that in? Maybe @clairernovotny knows? It seems not so bad to exclude those projects from rebuilding for a while though.
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.
The WPF issues with targets/props and source link should all be fixed by setting
IncludePackageReferencesDuringMarkupCompilation
to true in theDirectory.Build.Props
file and using a 5.0.200+ SDK to build. This enables fixes within the WPF targets that are currently opt-out.