You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See this all the time, the default Copy doesn't set SkipUnchangedFiles by default and therefore always runs even if the files haven't changed. This is not obvious. Here's an example of what I needed to set to make my Copy target friendly to MSBuild'isms:
The text was updated successfully, but these errors were encountered:
Forgind
added
help wanted
Issues that the core team doesn't plan to work on, but would accept a PR for. Comment to claim.
and removed
help wanted
Issues that the core team doesn't plan to work on, but would accept a PR for. Comment to claim.
labels
Aug 5, 2020
Yes please, let's set SkipUnchangedFiles to true by default. People who care about this setting will set it explicitly and not rely on the default. But I suspect the vast majority (if not everyone) not setting it aren't doing it on purpose.
See this all the time, the default Copy doesn't set SkipUnchangedFiles by default and therefore always runs even if the files haven't changed. This is not obvious. Here's an example of what I needed to set to make my Copy target friendly to MSBuild'isms:
dotnet/project-system#2253
The text was updated successfully, but these errors were encountered: