Framework Dependent Publish doesn't work on 2.1.400
See original GitHub issueSteps to reproduce
Try to publish web api with dotnet publish -f netcoreapp2.0 -c Release
, or within visual studio, with framework dependent selected
Expected behavior
Publish around 30 files
Actual behavior
Publishing over 200 files (self-contained)
Environment data
dotnet --info
output:
SDK do .NET Core (refletindo qualquer global.json): Version: 2.1.400 Commit: 8642e60a0f
Ambiente de tempo de execução: OS Name: Windows OS Version: 10.0.17134 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\2.1.400\
Host (useful for support): Version: 2.1.2 Commit: 811c3ce6c0
.NET Core SDKs installed: 2.1.202 [C:\Program Files\dotnet\sdk] 2.1.302 [C:\Program Files\dotnet\sdk] 2.1.400 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed: Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All] Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
Description
After upgrading to Visual Studio v15.8, which comes with .net core SDK v2.1.4, I’ve been trying to publish my WebAPI in a Framework Dependent way, but it only generates the Self Contained way, with over 200 files.
Issue Analytics
- State:
- Created 5 years ago
- Comments:28 (23 by maintainers)
Top GitHub Comments
@peterhuene Thank you for writing such a clean and informative commit history for future SDK engineers ❤️
@TatiTheFreaK another workaround if you don’t want to edit your project file is to publish with
dotnet publish -f netcoreapp2.0 -c Release --self-contained false
. The bug is thatSelfContained
should be implicitly set tofalse
, but it’s actually an empty string with the 2.1.4xx SDK. I have a fix ready that we hope to get into a 2.1.4xx servicing release. Thanks very much for reporting this issue to us!