PublishSingleFile with RuntimeIdentifiers fail to publish

@johnlarfour commented on Tue Jun 11 2019

linux/amd64 dotnet 3.0.100-preview5-011568

Step to reproduce:

dotnet new console -o app

Replace csproj with:

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp3.0</TargetFramework>
    <RuntimeIdentifiers>linux-x64;win-x86;osx-x64</RuntimeIdentifiers>
    <PublishSingleFile>true</PublishSingleFile>
  </PropertyGroup> 
</Project>

cd app
dotnet publish

Error:

/home/john/dotnet/sdk/3.0.100-preview5-011568/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.RuntimeIdentifierInference.targets(133,5): error NETSDK1097: It is not supported to publish an application to a single-file without specifying a RuntimeIdentifier. Please either specify a RuntimeIdentifier or set PublishSingleFile to false. [/home/john/Desktop/app/app.csproj]

[livarcocc]

You need to specify a single RuntimeIdentifier when publishing with Single File. The error message is correct and accurate in this case.

You can try to either edit your csproj to contain a single RuntimeIdentifier, like this

<RuntimeIdentifier>linux-x64</RuntimeIdentifier>

Or, you can pass the -r parameter to the dotnet publish command.

[secana]

This is really unexpected behavior. Any plans to change it? Running a dotnet publish for each runtime seems unnecessary if a RuntimeIdentifiers exists which could build for multiple runtimes at once.