Rainer Sigwald

> In case of `dotnet publish` and `"true"` `"false"` it's > >  For this callsite we definitely have some work to do spanifying the parsing, but the strings themselves...

I'm looking at fixing this in my fork already.

> Our .NET default yaml files for GitHub Actions and AzDO Pipelines break out into separate steps for restore, build, test, publish, etc. along with opted out of the implied...

> How about: > > ``` > dotnet restore --immutable-mode > dotnet build > dotnet build > dotnet build > dotnet publish > ``` > > That's looking much better....

That doesn't seem worth the cost of increasing the likelihood of an inconsistency failure in a later step, to me.

Sure, so I'd like to ensure "merge steps so you don't have inconsistencies" is on the table as an option.

> * Put your `Dockerfile` by your project or solution file and match your build context to that scope. Potentially miss MSBuild files in parent directories of your repo. I...

MSBuild does put everything on stdout. But I don't think that's the right design, and I'd rather go with the industry standard (primary output to stdout, warnings and errors to...

@kasper3 MSBuild [sets errorlevel](https://github.com/Microsoft/msbuild/blob/8fb642fe991be966599fe7110e36e6fb5208c498/src/MSBuild/XMake.cs#L215-L229), and I don't repro that: ``` s:\msbuild>msbuild non-existing.sln Microsoft (R) Build Engine version 15.7.66.2115 for .NET Framework Copyright (C) Microsoft Corporation. All rights reserved. MSBUILD :...

Yes, a binary log (or a diagnostic log) would be helpful here. It would probably be helpful even from a build that did not fail with this problem--I suspect that...