Daniel Plaisted

> Building using the preprocessed file rarely works for other reasons. So I discovered after fixing the `xmlns` :-)

@MichaelSimons Any idea why this would happen? I tried updating to the latest packages on Ubuntu 18 and it didn't give me any issues. The package version numbers look different...

I discussed this with @davkean yesterday. The proposal is that MSBuild would provide a list of SDKs to download. There are some cases where we couldn't know the full dependencies...

I'm not clear on the details of the problem. Do you have a repro? I also thought we had enforcement for something similar, you will get a build error if...

Try publishing the [StructuredLogViewer.Avalonia.csproj](https://github.com/KirillOsenkov/MSBuildStructuredLog/blob/main/src/StructuredLogViewer.Avalonia/StructuredLogViewer.Avalonia.csproj) project directly instead of the whole solution: ``` dotnet publish StructuredLogViewer.Avalonia.csproj --self-contained --runtime ubuntu.14.04-x64 ``` A different runtime identifier might work (better), I'm just going off...

@jeffkl Could you look at this again. I've switched it so that it logs to the SdkLogger, but only for resolution failures. It uses `FormattableString` now so it shouldn't be...

> This is a huge improvement. Will these be on by default? How will this look in a binlog or a text log? The current version of this PR will...

/azp run

@dotnet/msbuild Is it expected that `SdkResolverContext.Logger` would be null on Mac and Linux? That seems to be the case based on some of the [test failures](https://dev.azure.com/dnceng-public/public/_build/results?buildId=76742&view=ms.vss-test-web.build-test-results-tab&runId=1588690&resultId=101531&paneView=debug). EDIT: Never mind, it...

Here's a proposal for this to see if we can get it moving forward. What do people think? # Command line evaluation of MSBuild properties We will add command-line options...