.NET Core RuntimeIdentifier vs TargetFramework

Asked 20/4, 2017 at 12:34 Answered 24/7, 2024 at 8:25

asp.net-core .net-core visual-studio-2017 asp.net-core-webapi runtime-identifier

Can someone explain the purpose of these two in the csproj file (VS2017):

<TargetFramework>netstandard1.6</TargetFramework>
<RuntimeIdentifier>win7</RuntimeIdentifier>

I just migrated from VS2015 and now can't publish my web api because it looks I should use only one target framework. In addition I can't specify multiple RIDs. All these changed things make me frustrated. Nothing works from scratch, should overcome something over and over.

I just want developing my web-api on windows, run xUnit tests here and then deploy web-api to run on linux (ubuntu) server. What I should put in both parameters in csproj ? Links with good explanation is highly appreciated.

Update1

I have web api with referenced .net core libraries. Everything where migrated from VS2015. Now in root project I have <TargetFrameworks>netcoreapp1.1;net461</TargetFrameworks>. When I publish via VS2017 I got error:

C:\Program Files\dotnet\sdk\1.0.3\Sdks\Microsoft.NET.Sdk\buildCrossTargeting\Microsoft.NET.Sdk.targets(31,5): error : The 'Publish' target is not supported without specifying a target framework. The current project targets multiple frameworks, please specify the framework for the published application.

But I have specified target framework in publish as netcoreapp1.1. OK. Then I updated my csproj with <PropertyGroup Condition="$(TargetFramework)'=='netcoreapp1.1'"> <RuntimeIdentifier>ubuntu.16.10-x64</RuntimeIdentifier> </PropertyGroup> as suggested below. But now I even can't build app, get error:

5>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Sdks\Microsoft.NET.Sdk\build\Microsoft.NET.Sdk.targets(92,5): error : Assets file '\obj\project.assets.json' doesn't have a target for '.NETCoreApp,Version=v1.1/ubuntu.16.10-x64'. Ensure you have restored this project for TargetFramework='netcoreapp1.1' and RuntimeIdentifier='ubuntu.16.10-x64'.

I just want develop with VS2017 at windows 8.1/windows7 and deploy to ubuntu 16.10. What I'm doing wrong ?

Update2

I have 8 projects in solution. 3 of them are xUnit tests. Thus we have 5 projects. 4 of these 5 are class libraries and 1 is my web-app. All 4 class libraries have this:

<TargetFrameworks>netstandard1.6;net461</TargetFrameworks>    
<ItemGroup Condition=" '$(TargetFramework)' == 'net461' ">
    <Reference Include="System" />
    <Reference Include="Microsoft.CSharp" />
</ItemGroup>

My web app:

<TargetFrameworks>netcoreapp1.1;net461</TargetFrameworks>
<ItemGroup Condition=" '$(TargetFramework)' == 'net461' ">
    <Reference Include="System" />
    <Reference Include="Microsoft.CSharp" />
  </ItemGroup>

How to publish my web-app ?

Delmore answered 20/4, 2017 at 12:34 Comment(0)

The <TargetFramework> (or <TargetFrameworks> when you want have multiple targets, such as net451, one or multiple netstandard1.x etc). Per <TargetFramework> / <TargetFrameworks> entry one set of assemblies will be created and located inside bin\Debug\<targetframeworkid>).

This is useful, when you want to use a different library in .NET Core (because the library you used only works with full .NET Framework such as 4.5.1) or remove this feature from i.e. .NET Core because it's unsupported.

It is used for both, building and NuGet restore. i.e. you can't use a net451 only library in a .NET Core project (netstandard 1.1 for example - but you can use netstandard1.1 in a net451 project).

<RuntimeIdentifier> / <RuntimeIdentifiers> on the other side is used for NuGet mainly. It tells NuGet which packages you need. For example if you want to target Linux, Mac and Windows, certain assemblies require native libraries (such as encryption. On windows CryptoAPI will be used, but on Linux and Mac you need OpenSSL). This includes non-managed dlls and *.so (Linux) files.

i.e. <RuntimeIdentifiers>win7-x64;win7-x86;ubuntu.16.10-x64</RuntimeIdentifiers> will make nuget restore packages for win7 (both x64 and x86) versions and x64 only for ubuntu. This is required, because when you work on windows you need to download these native libraries too so you deploy/package them with dotnet publish.

Here's a little catch though: When you have a full .NET Framework reference in <TargetFramework> or <TargetFrameworks>, then you must specify a single <RuntimeIdentifier> (singular, not plural <RuntimeIdentifiers>), otherwise you will get an error.

For example:

<PropertyGroup>
    <TargetFrameworks>netstandard1.0;net451</TargetFrameworks>
    <RuntimeIdentifiers>win7-x64;win7-x86;ubuntu.16.10-x64</RuntimeIdentifiers>    
</PropertyGroup>

<!-- This entry will only be used for the .NET Framework 4.5.1 output -->
<PropertyGroup Condition="'$(TargetFramework)' == 'net451'">
    <RuntimeIdentifier>win7-x64</RuntimeIdentifier>
</PropertyGroup>

Diarmit answered 20/4, 2017 at 12:49 Comment(7)

<TargetFrameworks>netstandard1.0;net451</TargetFrameworks> is unnecessary when he using .Net Standard. You are using many outdated practices – Subconscious 20/4, 2017 at 13:8

I tried and it doesn't work for me. See my updates on the question. – Delmore 20/4, 2017 at 13:29

@Alezis: Read the message ;) When you have more than 1 target, you have to tell dotnet publish which version to publish. learn.microsoft.com/en-us/dotnet/articles/core/tools/…, i.e. dotnet publish --runtime ubuntu.16.10-x64. Also in netstandard1.0;net451 the net451 is obsolete (since netstandard1.0 runs on .NET 4.5 and higher. But if you use features only available in 1.3 (.NET 4.6), then netstandard1.3;net451 can be used to create two builds. See learn.microsoft.com/en-us/dotnet/articles/standard/library – Diarmit 20/4, 2017 at 13:32

@Diarmit Thanks for you help, but it doesn't work either. I run dotnet publish --runtime ubuntu.16.10-x64 and get the same error. Also as I said my root app (web-app) targets netcoreapp1.1;net461. I don't use net451 just 3 items netcoreapp1.1 net461 netstandard1.6 in all my 5 projects. – Delmore 20/4, 2017 at 13:44

@Delmore Not better just use netstandard1.6 and then dotnet publish -c release -r ubuntu.16.10-x64? – Subconscious 20/4, 2017 at 14:5

Unfortunately @J.Doe there are quite a lot of places where netstandard on it's own is not sufficient -- if you are referencing the System.Drawing.Common library for instance, then (as of November, 2018) you have to cross-compile targeting net462 (or higher) and netstandard separately. – Jhvh 13/11, 2018 at 21:24

I am using RuntimeIdentifier along with PublishSingleFile to create .exe files for easy testing while dev. Is there a way to say RuntimeIdentifier is the current platform under which we compile? I want to avoid hard-coding them – Multifaceted 4/12, 2019 at 21:28

RID is short for Runtime IDentifier. RIDs are used to identify target operating systems where an application or asset (that is, assembly) will run. They look like this: "ubuntu.14.04-x64", "win7-x64", "osx.10.11-x64". For the packages with native dependencies, it will designate on which platforms the package can be restored.

Example

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <!-- OTHER PROPERTIES -->
    <Platforms>Win-x86;Win-x64;Linux-x64</Platforms>
    <OutputPath>bin/$(TargetPlatform)/$(RuntimeIdentifier)</OutputPath>
  </PropertyGroup>
  <PropertyGroup Condition="'$(Platform)' == 'Win-x86'">
    <TargetFramework>net481</TargetFramework>
    <RuntimeIdentifier>win-x86</RuntimeIdentifier>
  </PropertyGroup>
  <PropertyGroup Condition="'$(Platform)' == 'Win-x64'">
    <TargetFrameworks>net481;net6.0</TargetFrameworks>
    <RuntimeIdentifier>win-x64</RuntimeIdentifier>
  </PropertyGroup>
  <PropertyGroup Condition="'$(Platform)' == 'Linux-x64'">
    <TargetFramework>net6.0</TargetFramework>
    <RuntimeIdentifier>ubuntu.16.10-x64</RuntimeIdentifier>
  </PropertyGroup>
  <!-- ... -->

Sachasachem answered 24/7, 2024 at 8:25 Comment(0)

Hot tags

Godot Unity Godot Help Programming Godot 4.X GUI GDScript 3D 2D Physics CSharp Godot 3.X VR XR Projects C++

Example

Recommended topics

Hot tags