Daniel Plaisted

Is there any concern that this could break projects (most likely with custom MSBuild logic) that weren't expecting reference assemblies to be enabled? For C#, we only enabled reference assemblies...

Library authors shouldn't necessarily be targeting .NET Standard, especially as time goes on: https://devblogs.microsoft.com/dotnet/the-future-of-net-standard/#what-you-should-target

@Structed The leftover process is expected. You can shut down such processes with `dotnet build-server shutdown`. If the leftover process is locking files causing subsequent builds to fail, then that...

@Structed Yes, please provide the logs and repro project if possible.

> Has anything ever come out of this? > I have a group of about 200 assemblies. Running DOTNET on each project is WAY too slow so I put them...

@southrivertech It looks to me like the issue here has to do with running `dotnet publish` (and possibly also `dotnet build`) on a solution while trying to specify the TargetFramework....

Hi @komdil, Let me try to explain what is happening. Normally each project builds to a different output folder. When there is a ProjectReference between projects, the referencing project copies...

Here's the reasoning behind that from the [original design](https://github.com/dotnet/designs/blob/main/accepted/2020/net5/net5.md#why-is-there-no-tfm-for-linux): > ### Why is there no TFM for Linux? > > The primary reason for OS specific TFMs is to vary...

I tried the repro steps on Windows and it worked OK. @marcpopMSFT, could someone with a Mac try reproing this?

Yes, `--sdk-version` may well be broken. It is broken for printing the download links, and #27064 should fix that, though I'm not sure it will fix it for actual installation....