You can set the following in your .csproj to disable this behavior.
<PropertyGroup> <AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath> </PropertyGroup>
https://github.com/NuGet/Home/issues/4488
This is going to be a very common scenario. People are creating new .NET Standard projects and will add p2p refs to them from their existing "legacy" projects. -- Xamarin, Desktop, etc.
The right binaries won‘t be in the output directory and people will be confused by this broken behavior.
The only workaround is that you have to add <RestoreProjectStyle>PackageReference</RestoreProjectStyle> to the legacy project.
Can't remove netstandard folder from output path
原文：https://www.cnblogs.com/chucklu/p/9372777.html