Jan Krivanek
> > ... except for cases where the property is tested in a condition like so `'$(MyProp)' == ''` > > My preference is to further specialize this by stating...
The `MSBuild` prefix might want to be included as well (https://github.com/dotnet/msbuild/pull/10102#discussion_r1598285182)
We might seed this with some initial list of reserved properties (beyond the `'_'` prefix), plus an optional custom configuration key - something like 'forbidden_write_properties_csv'
I like that idea. (all those rules would still be contained within single executing BuildCheck)
@nohwnd - let's discuss if your team still has the need for pre and post solution build steps - so we can see if offered options are sufficient.
Is this expected to as well address https://github.com/dotnet/msbuild/issues/6566 and https://github.com/dotnet/msbuild/issues/7988?
As for the `$(DevEnvDir)` usage - https://github.com/dotnet/msbuild/issues/9885 would catch this. But it's a nice idea to have a sepacialized check. @rainersigwald - can you please specify more the scenario with...
The whitelist/blacklist locations should be configurable here. But in general outside of current repo cone, nuget cache (and sdk) the refs might lead to reproducibility issues. Possibly the sdk side...
The PR that stop gapped the CopyTask output in TerminalLogger: https://github.com/dotnet/msbuild/pull/10296 This item is proposing improved UX for that