Publishing to win10-arm or win8-arm doesn't generate an exe file for a Console application

Steps to recreate issue First I created a dotnetcore 2.0 console app, and added nodes for the RuntimeFrameworkVersion and RuntimeIdentifiers to the csproj file, as shown in the csproj file below.

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp2.0</TargetFramework>
    <RuntimeFrameworkVersion>2.0.0-preview1-002111-00</RuntimeFrameworkVersion>
    <RuntimeIdentifiers>win10-arm;win10-x64</RuntimeIdentifiers>
  </PropertyGroup>

</Project>

Then restore and build this project (using “dotnet restore” and “dotnet build”). Now publish with the target of win10-arm using “dotnet publish -r win10-arm” Look in the netcoreapp2.0/win10-arm/publish for the output executable.

Actual Behavior After restoring and building, when I run “dotnet publish -r win10-arm”, there is not a ConsoleApp.exe file in the netcoreapp2.0/win10-arm/publish directory - there’s only a ConsoleApp.dll file. I’ve tried this for win8-arm as well with the same results.

Everything builds fine in both win10-arm and win10-x64 configurations using “dotnet restore” and “dotnet build” - no errors.

When I run “dotnet publish -r win10-x64”, as expected there is a ConsoleApp.exe file in the netcoreapp2.0/win10-x64/publish directory.

Expected behaviour I think the expected behaviour is to see a ConsoleApp.exe in the netcoreapp2.0/win10-arm/publish directory when I publish and target win8-arm or win10-arm. Dotnet core used to create an executable file - I’m running my application on the “Windows 10 IoT Core” framework on the Raspberry Pi 3, and have used a generated ConsoleApp.exe file for .net core apps on the Pi. There’s not an option to run “dotnet ConsoleApp.dll” on Pi running Windows 10 IoT Core.

Jeremy

[eerhardt]

@jeremylindsayni - yes! We would be more than happy to review a PR to add an ARM test to the SDK. That’s a great idea.

Welcome aboard!

[eerhardt]

Looks like the issue is with our RID graph and win10-arm not importing win-arm correctly.

win10-arm => win81-arm => win8-arm, however it ends there.

https://github.com/dotnet/corefx/blob/master/pkg/Microsoft.NETCore.Platforms/runtime.json#L59-L61

I think

        "win8-arm": {
            "#import": [ "win8" ]
        },

should be

        "win8-arm": {
            "#import": [ "win8", "win-arm" ]
        },

@ericstj @weshaggard @gkhanna79 - is there a specific reason for this? Or is this just an oversight?

If this is an oversight, I can open a PR for this in master, and get shiproom approval for 2.0.

@jeremylindsayni - the workaround for now is instead of using win10-arm to use win-arm as your RID.