Chet Husk

@lagomesma are there specific commands that we should focus on the semantics of? I can get on board an interpretation of "dotnet run should map all build related output to...

Thanks for the feedback @lagomesma! I definitely agree that there's a place here for guidance around the proper use of stdout/stderr for tools that ship in or around the SDK...

From what I can tell, yes! And this is something that I'd expect to be the case with _all_ commands that aren't Powershell Cmdlets specifically

This appears to be because `BeforePublish` and `AfterPublish` are only defined for Web SDK projects, not the .NET SDK itself. They are defined [here](https://github.com/dotnet/sdk/blob/a4431a389bbea6b1126c004368cd61c9d16a4c49/src/WebSdk/Publish/Targets/Microsoft.NET.Sdk.Publish.targets#L41-L43). We probably should pull this down...

This one slipped through the cracks - I've added it to our triage bucket for discussion. As I stated above, I definitely believe that we need to do this work...

This was likely introduced in https://github.com/dotnet/sdk/pull/26204, which itself was fixing a regression. We should extend the testing matrix for MSBuild property forwarding and cover this case, which is fairly unique...

Yep! This just wasn't closed when the linked PR merged. I'll do so now.

We can't take this in main, because the version of F# referenced in this repo hasn't advanced to the point where that is available. I think F# is doing codeflow...

I think so - specifically that the F# team inserts a version of their tools that is compatible with this into VS previews. @vzarytovskii do you have any insight into...

@nojaf this is too late for rc1, we're very far past code freeze at this point. This should be retargeted to `release/7.0.1xx` for inclusion in RC2.