-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add deps and runtime configuration files to @(FileWrites) so they are deleted during Clean #381
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
… deleted during Clean Fixes dotnet#305
5770771 to
c6d3128
Compare
|
@rainersigwald, can you check to see if it looks like this is integrating with the |
|
|
||
| <Target Name="GenerateBuildDependencyFile" | ||
| DependsOnTargets="_DefaultMicrosoftNETPlatformLibrary" | ||
| BeforeTargets="_CheckForCompileOutputs" |
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.
My instinct would be to go before _CleanGetCurrentAndPriorFileWrites instead, since this isn't really compile-specific. But _CheckForCompileOutputs is before that so this is ok. Did you prefer this for a reason?
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.
Wouldn't this cause GenerateBuildDependencyFile to run on Clean? That's not right. We want it to only run on build and log the write then.
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.
Wouldn't this cause GenerateBuildDependencyFile to run on Clean?
The IncrementalClean target runs during a normal build (CoreBuild depends on it). IncrementalClean depends on _CleanGetCurrentAndPriorFileWrites, which depends on _CheckForCompileOutputs. So it's confusing (which is why I asked for Rainier's review), but I think it's doing the right thing and not causing this to run during Clean.
Did you prefer this for a reason?
I think it was because GenerateBuildDependencyFile also writes files to the output folder, so I thought it might make sense to be before the CopyFilesToOutputDirectory target, which depends on _CheckForCompileOutputs.
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.
Ah ok
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.
^ that meshes with my reasoning on @nguerrera's question. 👍
|
|
||
| <Target Name="GenerateBuildDependencyFile" | ||
| DependsOnTargets="_DefaultMicrosoftNETPlatformLibrary" | ||
| BeforeTargets="_CheckForCompileOutputs" |
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.
Wouldn't this cause GenerateBuildDependencyFile to run on Clean? That's not right. We want it to only run on build and log the write then.
|
@MattGertz for approval ScenarioCleaning a project should delete all files that building it put in the output folder BugWorkaroundsDelete files manually, or just ignore that clean doesn't clean everything RiskLow - Tests should cover any impacted scenarios Performance ImpactLow - the change is only writing 3 additional lines to a file that is already written during build, and deleting 3 files during clean Regression AnalysisNot a regression |
|
Approved. |
Update the ReadMe with build status
Fixes #305