Rainer Sigwald

@jianyexi I think several of the problems you're encountering could be resolved by generating the files into a folder in the `obj` (`$(IntermediateOutputPath)`) directory, instead of next to the checked-in...

@jianyexi yes, via SDK properties you can change the files that are automatically discovered under the project; see [`DefaultItemExcludes`](https://docs.microsoft.com/dotnet/core/project-sdk/msbuild-props#defaultitemexcludes) for example.

I support this: `CopyAlways` is a footgun. The error message actually might be a bit annoying, because it should ideally be localized. SDK has a task to emit localized errors,...

> Could MSBuild just treat `Always` as `IfDifferent`? This should address the perf issue without breaking the only known use case for `Always` I've seen. We definitely can. The existing...

We shouldn't be in that "none" mode for any .NET SDK scenario, I don't think, so it's probably our problem in an earlier codepath.

MSBuild Team triage: we like the proposal, @jrdodds. > ❓ Should empty directories be copied? > > With the following code, empty directories are not included and are not copied....

From the text I infer that the issue is really about understanding which of potentially multiple configurations (global property sets) of a specific project a message is coming from. That...

That's not batching--the giveaway is that there's nothing in the form `%(ItemName.MetadataName)`. That's just a parallel MSBuild call, more or less like a `Parallel.Foreach`--batching is more like a regular serial...

Team triage: We'd like to improve this. But people do grep through logs, so it's a breaking change. Tentative plan: 1. Improve console/text logging behind an opt-in flag (environment variable?)...

https://github.com/dotnet/sdk/pull/12030 needs to be brought back to get this done.