From 231b0d3799b6752d39da91e7ce70e7e51e2a47b3 Mon Sep 17 00:00:00 2001 From: Maira Wenzel Date: Tue, 20 Jun 2017 19:00:39 -0700 Subject: [PATCH 1/7] updates --- docs/core/rid-catalog.md | 66 ++++++++++++++++++---------------------- 1 file changed, 30 insertions(+), 36 deletions(-) diff --git a/docs/core/rid-catalog.md b/docs/core/rid-catalog.md index 596b9a8867e93..4e9e505f89c18 100644 --- a/docs/core/rid-catalog.md +++ b/docs/core/rid-catalog.md @@ -1,52 +1,51 @@ --- title: .NET Core Runtime IDentifier (RID) catalog | Microsoft Docs -description: .NET Core Runtime IDentifier (RID) catalog +description: keywords: .NET, .NET Core author: blackdwarf ms.author: mairaw -ms.date: 08/22/2016 +ms.date: 06/20/2017 ms.topic: article ms.prod: .net-core ms.devlang: dotnet ms.assetid: b2032f5d-771f-48d9-917c-587d9509035c --- - # .NET Core Runtime IDentifier (RID) catalog -## What are RIDs? 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. +(that is, assembly) runs. The following are examples of RIDs: `ubuntu.14.04-x64`, `win7-x64`, or `osx.10.11-x64`. +For the packages with native dependencies, it designates on which platforms the package can be restored. -It is important to note that RIDs are really opaque strings. This means that they have to match exactly for operations -using them to work. As an example, let us consider the case of [Elementary OS](https://elementary.io/), which is a straightforward clone of -Ubuntu 14.04. Although .NET Core and CLI work on top of that version of Ubuntu, if you try to use them on Elementary OS -without any modifications, the restore operation for any package will fail. This is because we currently don't -have a RID that designates Elementary OS as a platform. +It's important to note that RIDs are opaque strings, that is, they have to match exactly for operations +using them to work. As an example, let's consider the case of the [elementary OS Loki](https://elementary.io/), +which is an OS version based on Ubuntu 16.04. Even though .NET Core and CLI work on top of that Ubuntu version, if you try to use them on elementary OS +without any modifications, the restore operation for any package will fail. This happens because we currently don't +have a RID that designates elementary OS as a platform. RIDs that represent concrete operating systems usually follow this pattern: `[os].[version]-[arch]` where: -- `[os]` is the operating system moniker, for example, `ubuntu`. -- `[version]` is the operating system version in the form of a dot (`.`) separated version number, for example, `15.10`, -accurate enough to reasonably enable assets to target operating system platform APIs represented by that version. - - This **shouldn't** be marketing versions, as they often represent multiple discrete versions of the operating +- `[os]` is the operating system moniker. For example, `ubuntu`. +- `[version]` is the operating system version in the form of a dot-separated (`.`) version number. For example, `15.10`. +Accurate enough to reasonably enable assets to target OS platform APIs represented by that version. + - The version **shouldn't** be marketing versions, as they often represent multiple discrete versions of the operating system with varying platform API surface area. -- `[arch]` is the processor architecture, for example, `x86`, `x64`, `arm`, `arm64`, etc. +- `[arch]` is the processor architecture. For example: `x86`, `x64`, `arm`, or `arm64`. The RID graph is defined in a package called `Microsoft.NETCore.Platforms` in a file called `runtime.json`, which you can see on the [CoreFX repo](https://github.com/dotnet/corefx/blob/master/pkg/Microsoft.NETCore.Platforms/runtime.json). If -you use this file, you will notice that some of the RIDs have an `"#import"` statement in them. These statements are -compatibility statements. That means that a RID that has an imported RID in it can be a target for restoring packages -for that RID. Slightly confusing, but let's look at an example. Let's take a look at macOS: +you open this file, you can see that some of the RIDs have an `"#import"` statement in them. These statements are +compatibility statements. That means that an RID that contains an imported RID can be a target for restoring packages +for that RID. Slightly confusing, but let's look at an example for a macOS RID: ```json "osx.10.11-x64": { "#import": [ "osx.10.11", "osx.10.10-x64" ] } ``` -The above RID specifies that `osx.10.11-x64` imports `osx.10.10-x64`. This means that when restoring packages, NuGet will -be able to restore packages that specify that they need `osx.10.10-x64` on `osx.10.11-x64`. -A slightly bigger example RID graph: +The above RID specifies that `osx.10.11-x64` imports `osx.10.10-x64`. When NuGet restores packages, it +can restore packages that specify that they need `osx.10.10-x64` on `osx.10.11-x64`. + +The following example shows a slightly bigger RID graph: - `win10-arm` - `win10` @@ -60,22 +59,17 @@ A slightly bigger example RID graph: All RIDs eventually map back to the root `any` RID. -Although they look easy enough to use, there are some special things about RIDs that you have to keep in mind when +Although they look easy enough to use, there are some considerations about RIDs that you have to keep in mind when working with them: -* They are **opaque strings** and should be treated as black boxes - * You should not construct RIDs programmatically -* You need to use the RIDs that are already defined for the platform and this document shows that -* The RIDs do need to be specific so don't assume anything from the actual RID value; please consult this document -to determine which RID(s) you need for a given platform +* They are **opaque strings** and should be treated as black boxes. +* Don't build RIDs programmatically. +* Use RIDs that are already defined for the platform. +* The RIDs need to be specific, so don't assume anything from the actual RID value. ## Using RIDs -In order to use RIDs, you have to know which RIDs there are. New RIDs are added regularly to the platform. -For the latest version, please check the [runtime.json](https://github.com/dotnet/corefx/blob/master/pkg/Microsoft.NETCore.Platforms/runtime.json) file on CoreFX repo. - -> [!NOTE] -> We are working towards getting this information into a more interactive form. -> When that happens, this page will be updated to point to that tool and/or its usage documentation. +To be able to use RIDs, you have to know which RIDs exist. New values are added regularly to the platform. +For the latest version, see the [runtime.json](https://github.com/dotnet/corefx/blob/master/pkg/Microsoft.NETCore.Platforms/runtime.json) file on CoreFX repo. ## Windows RIDs @@ -114,7 +108,7 @@ For the latest version, please check the [runtime.json](https://github.com/dotne * Fedora * `fedora.23-x64` * `fedora.24-x64` -* OpenSUSE +* openSUSE * `opensuse.13.2-x64` * `opensuse.42.1-x64` * Oracle Linux @@ -133,4 +127,4 @@ For the latest version, please check the [runtime.json](https://github.com/dotne * `osx.10.10-x64` * `osx.10.11-x64` -* `osx.10.12-x64` +* `osx.10.12-x64`: can only be used in .NET Core 1.1 or later versions applications. From 14f48a0d29bc4bfd439ba07fbbc77b89708ac549 Mon Sep 17 00:00:00 2001 From: Maira Wenzel Date: Thu, 7 Sep 2017 00:24:43 -0700 Subject: [PATCH 2/7] updates for 2.0 --- docs/core/rid-catalog.md | 248 +++++++++++++++++++++++---------------- 1 file changed, 147 insertions(+), 101 deletions(-) diff --git a/docs/core/rid-catalog.md b/docs/core/rid-catalog.md index 4e9e505f89c18..dcf4603b34a97 100644 --- a/docs/core/rid-catalog.md +++ b/docs/core/rid-catalog.md @@ -1,40 +1,48 @@ --- -title: .NET Core Runtime IDentifier (RID) catalog | Microsoft Docs -description: -keywords: .NET, .NET Core -author: blackdwarf +title: .NET Core Runtime IDentifier (RID) catalog +description: Runtime identifiers (RIDs) identify target platforms where the application runs. Learn more about them and see a list of common RID values. +author: mairaw ms.author: mairaw -ms.date: 06/20/2017 +ms.date: 09/07/2017 ms.topic: article ms.prod: .net-core -ms.devlang: dotnet -ms.assetid: b2032f5d-771f-48d9-917c-587d9509035c --- -# .NET Core Runtime IDentifier (RID) catalog - -RID is short for *Runtime IDentifier*. RIDs are used to identify target operating systems where an application or asset -(that is, assembly) runs. The following are examples of RIDs: `ubuntu.14.04-x64`, `win7-x64`, or `osx.10.11-x64`. -For the packages with native dependencies, it designates on which platforms the package can be restored. - -It's important to note that RIDs are opaque strings, that is, they have to match exactly for operations -using them to work. As an example, let's consider the case of the [elementary OS Loki](https://elementary.io/), -which is an OS version based on Ubuntu 16.04. Even though .NET Core and CLI work on top of that Ubuntu version, if you try to use them on elementary OS -without any modifications, the restore operation for any package will fail. This happens because we currently don't -have a RID that designates elementary OS as a platform. - -RIDs that represent concrete operating systems usually follow this pattern: `[os].[version]-[arch]` where: -- `[os]` is the operating system moniker. For example, `ubuntu`. -- `[version]` is the operating system version in the form of a dot-separated (`.`) version number. For example, `15.10`. -Accurate enough to reasonably enable assets to target OS platform APIs represented by that version. - - The version **shouldn't** be marketing versions, as they often represent multiple discrete versions of the operating -system with varying platform API surface area. -- `[arch]` is the processor architecture. For example: `x86`, `x64`, `arm`, or `arm64`. - -The RID graph is defined in a package called `Microsoft.NETCore.Platforms` in a file called `runtime.json`, which you can -see on the [CoreFX repo](https://github.com/dotnet/corefx/blob/master/pkg/Microsoft.NETCore.Platforms/runtime.json). If -you open this file, you can see that some of the RIDs have an `"#import"` statement in them. These statements are -compatibility statements. That means that an RID that contains an imported RID can be a target for restoring packages -for that RID. Slightly confusing, but let's look at an example for a macOS RID: +# .NET Core RID Catalog + +RID is short for *Runtime IDentifier*. RID values are used to identify target platforms where the application runs. +They're used by .NET packages to represent runtime-specific assets in NuGet packages. The following values are examples of RIDs: `linux-x64`, `ubuntu.14.04-x64`, `win7-x64`, or `osx.10.11-x64`. +For the packages with native dependencies, the RID designates on which platforms the package can be restored. + +RIDs can be set in the `` element of your project file. They're also used via the `--runtime` option with the following [.NET Core CLI commands](./tools/index.md): + +- [dotnet build](./tools/dotnet-build.md) +- [dotnet clean](./tools/dotnet-clean.md) +- [dotnet pack](./tools/dotnet-pack.md) +- [dotnet publish](./tools/dotnet-publish.md) +- [dotnet restore](./tools/dotnet-restore.md) +- [dotnet run](./tools/dotnet-run.md) +- [dotnet store](./tools/dotnet-store.md) + +RIDs that represent concrete operating systems usually follow this pattern: `[os].[version]-[architecture]-[additional qualifiers]` where: + +- `[os]` is the operating/platform system moniker. For example, `ubuntu`. + +- `[version]` is the operating system version in the form of a dot-separated (`.`) version number. For example, `15.10`. + + - The version **shouldn't** be marketing versions, as they often represent multiple discrete versions of the operating system with varying platform API surface area. + +- `[architecture]` is the processor architecture. For example: `x86`, `x64`, `arm`, or `arm64`. + +- `[additional qualifiers]` further differentiate different platforms. For example: `aot` or `corert`. + +## RID graph + +The RID graph or runtime fallback graph is a list of RIDs that are compatible with each other. The RIDs are defined in the [Microsoft.NETCore.Platforms](https://www.nuget.org/packages/Microsoft.NETCore.Platforms/) package. You can see the list of supported RIDs and the RID graph in the [*runtime.json*](https://github.com/dotnet/corefx/blob/master/pkg/Microsoft.NETCore.Platforms/runtime.json) file, which is located at the CoreFX repo. In this file, you can see that all RIDs, except for the base one, contain an `"#import"` statement. These statements indicate compatible RIDs. + +When NuGet restores packages, it tries to find an exact match for the specified runtime. +If an exact match is not found, NuGet walks back the graph until it finds the closest compatible system according to the RID graph. + +The following example is the actual entry for the `osx.10.11-x64` RID: ```json "osx.10.11-x64": { @@ -42,89 +50,127 @@ for that RID. Slightly confusing, but let's look at an example for a macOS RID: } ``` -The above RID specifies that `osx.10.11-x64` imports `osx.10.10-x64`. When NuGet restores packages, it -can restore packages that specify that they need `osx.10.10-x64` on `osx.10.11-x64`. +The above RID specifies that `osx.10.11-x64` imports `osx.10.10-x64`. So, when NuGet restores packages, it tries to find an exact match for `osx.10.11-x64` in the package. If NuGet cannot find the specific runtime, it can restore packages that specify `osx.10.10-x64` runtimes, for example. -The following example shows a slightly bigger RID graph: +The following example shows a slightly bigger RID graph also defined in the *runtime.json* file: -- `win10-arm` - - `win10` - - `win81-arm` - - `win81` - - `win8-arm` - - `win8` - - `win7` - - `win` - - `any` +``` + win7-x64 win7-x86 + | \ / | + | win7 | + | | | + win-x64 | win-x86 + \ | / + win + | + any +``` All RIDs eventually map back to the root `any` RID. -Although they look easy enough to use, there are some considerations about RIDs that you have to keep in mind when -working with them: +There are some considerations about RIDs that you have to keep in mind when working with them: -* They are **opaque strings** and should be treated as black boxes. -* Don't build RIDs programmatically. -* Use RIDs that are already defined for the platform. -* The RIDs need to be specific, so don't assume anything from the actual RID value. +- RIDs are **opaque strings** and should be treated as black boxes. +- Don't build RIDs programmatically. +- Use RIDs that are already defined for the platform. +- The RIDs need to be specific, so don't assume anything from the actual RID value. ## Using RIDs -To be able to use RIDs, you have to know which RIDs exist. New values are added regularly to the platform. -For the latest version, see the [runtime.json](https://github.com/dotnet/corefx/blob/master/pkg/Microsoft.NETCore.Platforms/runtime.json) file on CoreFX repo. + +To be able to use RIDs, you have to know which RIDs exist. New values are added regularly to the platform. +For the latest and complete version, see the [runtime.json](https://github.com/dotnet/corefx/blob/master/pkg/Microsoft.NETCore.Platforms/runtime.json) file on CoreFX repo. + +.NET Core 2.0 SDK introduces the concept of portable RIDs. They are new values added to the RID graph that aren't tied to a specific version or OS distribution. They're particularly useful when dealing with the multiple Linux distros. + +The following list shows the most common RIDs used for each OS. It doesn't cover `arm` or `corert` values. ## Windows RIDs -* Windows 7 / Windows Server 2008 R2 - * `win7-x64` - * `win7-x86` -* Windows 8 / Windows Server 2012 - * `win8-x64` - * `win8-x86` - * `win8-arm` -* Windows 8.1 / Windows Server 2012 R2 - * `win81-x64` - * `win81-x86` - * `win81-arm` -* Windows 10 / Windows Server 2016 - * `win10-x64` - * `win10-x86` - * `win10-arm` - * `win10-arm64` +- Portable + - `win-x86` + - `win-x64` +- Windows 7 / Windows Server 2008 R2 + - `win7-x64` + - `win7-x86` +- Windows 8 / Windows Server 2012 + - `win8-x64` + - `win8-x86` + - `win8-arm` +- Windows 8.1 / Windows Server 2012 R2 + - `win81-x64` + - `win81-x86` + - `win81-arm` +- Windows 10 / Windows Server 2016 + - `win10-x64` + - `win10-x86` + - `win10-arm` + - `win10-arm64` ## Linux RIDs -* Red Hat Enterprise Linux - * `rhel.7-x64` -* Ubuntu - * `ubuntu.14.04-x64` - * `ubuntu.14.10-x64` - * `ubuntu.15.04-x64` - * `ubuntu.15.10-x64` - * `ubuntu.16.04-x64` - * `ubuntu.16.10-x64` -* CentOS - * `centos.7-x64` -* Debian - * `debian.8-x64` -* Fedora - * `fedora.23-x64` - * `fedora.24-x64` -* openSUSE - * `opensuse.13.2-x64` - * `opensuse.42.1-x64` -* Oracle Linux - * `ol.7-x64` - * `ol.7.0-x64` - * `ol.7.1-x64` - * `ol.7.2-x64` -* Currently supported Ubuntu derivatives - * `linuxmint.17-x64` - * `linuxmint.17.1-x64` - * `linuxmint.17.2-x64` - * `linuxmint.17.3-x64` - * `linuxmint.18-x64` +- Portable + - `linux-x64` +- Red Hat Enterprise Linux + - `rhel-x64` + - `rhel.6-x64` (.NET Core 2.0 or later versions) + - `rhel.7-x64` + - `rhel.7.1-x64` + - `rhel.7.2-x64` + - `rhel.7.3-x64` (.NET Core 2.0 or later versions) + - `rhel.7.4-x64` (.NET Core 2.0 or later versions) +- Ubuntu + - `ubuntu-x64` + - `ubuntu.14.04-x64` + - `ubuntu.14.10-x64` + - `ubuntu.15.04-x64` + - `ubuntu.15.10-x64` + - `ubuntu.16.04-x64` + - `ubuntu.16.10-x64` +- CentOS + - `centos-x64` + - `centos.7-x64` +- Debian + - `debian-x64` + - `debian.8-x64` +- Fedora + - `fedora-x64` + - `fedora.23-x64` + - `fedora.24-x64` + - `fedora.25-x64` (.NET Core 2.0 or later versions) + - `fedora.26-x64` (.NET Core 2.0 or later versions) +- openSUSE + - `opensuse-x64` + - `opensuse.13.2-x64` + - `opensuse.42.1-x64` +- Oracle Linux + - `ol-x64` + - `ol.7-x64` + - `ol.7.0-x64` + - `ol.7.1-x64` + - `ol.7.2-x64` +- Tizen (.NET Core 2.0 or later versions) + - `tizen` +- Gentoo (.NET Core 2.0 or later versions) + - `gentoo-x64` +- Currently supported Ubuntu derivatives + - `linuxmint.17-x64` + - `linuxmint.17.1-x64` + - `linuxmint.17.2-x64` + - `linuxmint.17.3-x64` + - `linuxmint.18-x64` + - `linuxmint.18.1-x64` (.NET Core 2.0 or later versions) ## OS X RIDs -* `osx.10.10-x64` -* `osx.10.11-x64` -* `osx.10.12-x64`: can only be used in .NET Core 1.1 or later versions applications. +- `osx-x64` (.NET Core 2.0 or later versions) +- `osx.10.10-x64` +- `osx.10.11-x64` +- `osx.10.12-x64` (.NET Core 1.1 or later versions) + +## Android RIDs (.NET Core 2.0 or later versions) + +- `android` +- `android.21` + +## See also + [Runtime IDs](https://github.com/dotnet/corefx/blob/master/pkg/Microsoft.NETCore.Platforms/readme.md) \ No newline at end of file From 3656c6c15eb8f9d56b525e4e7695046725ded093 Mon Sep 17 00:00:00 2001 From: Maira Wenzel Date: Thu, 7 Sep 2017 00:33:59 -0700 Subject: [PATCH 3/7] livefyre comment --- docs/core/rid-catalog.md | 40 ++++++++++++++++++++-------------------- 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/docs/core/rid-catalog.md b/docs/core/rid-catalog.md index 371f79e78ec46..94bdb00b8d2fa 100644 --- a/docs/core/rid-catalog.md +++ b/docs/core/rid-catalog.md @@ -110,22 +110,6 @@ The following list shows the most common RIDs used for each OS. It doesn't cover - Portable - `linux-x64` -- Red Hat Enterprise Linux - - `rhel-x64` - - `rhel.6-x64` (.NET Core 2.0 or later versions) - - `rhel.7-x64` - - `rhel.7.1-x64` - - `rhel.7.2-x64` - - `rhel.7.3-x64` (.NET Core 2.0 or later versions) - - `rhel.7.4-x64` (.NET Core 2.0 or later versions) -- Ubuntu - - `ubuntu-x64` - - `ubuntu.14.04-x64` - - `ubuntu.14.10-x64` - - `ubuntu.15.04-x64` - - `ubuntu.15.10-x64` - - `ubuntu.16.04-x64` - - `ubuntu.16.10-x64` - CentOS - `centos-x64` - `centos.7-x64` @@ -138,6 +122,8 @@ The following list shows the most common RIDs used for each OS. It doesn't cover - `fedora.24-x64` - `fedora.25-x64` (.NET Core 2.0 or later versions) - `fedora.26-x64` (.NET Core 2.0 or later versions) +- Gentoo (.NET Core 2.0 or later versions) + - `gentoo-x64` - openSUSE - `opensuse-x64` - `opensuse.13.2-x64` @@ -148,11 +134,25 @@ The following list shows the most common RIDs used for each OS. It doesn't cover - `ol.7.0-x64` - `ol.7.1-x64` - `ol.7.2-x64` +- Red Hat Enterprise Linux + - `rhel-x64` + - `rhel.6-x64` (.NET Core 2.0 or later versions) + - `rhel.7-x64` + - `rhel.7.1-x64` + - `rhel.7.2-x64` + - `rhel.7.3-x64` (.NET Core 2.0 or later versions) + - `rhel.7.4-x64` (.NET Core 2.0 or later versions) - Tizen (.NET Core 2.0 or later versions) - `tizen` -- Gentoo (.NET Core 2.0 or later versions) - - `gentoo-x64` -- Currently supported Ubuntu derivatives +- Ubuntu + - `ubuntu-x64` + - `ubuntu.14.04-x64` + - `ubuntu.14.10-x64` + - `ubuntu.15.04-x64` + - `ubuntu.15.10-x64` + - `ubuntu.16.04-x64` + - `ubuntu.16.10-x64` +- Ubuntu derivatives - `linuxmint.17-x64` - `linuxmint.17.1-x64` - `linuxmint.17.2-x64` @@ -173,4 +173,4 @@ The following list shows the most common RIDs used for each OS. It doesn't cover - `android.21` ## See also - [Runtime IDs](https://github.com/dotnet/corefx/blob/master/pkg/Microsoft.NETCore.Platforms/readme.md) \ No newline at end of file + [Runtime IDs](https://github.com/dotnet/corefx/blob/master/pkg/Microsoft.NETCore.Platforms/readme.md) From 3b7176e5b69d016ab8f3b6244c39a3dc58362744 Mon Sep 17 00:00:00 2001 From: Maira Wenzel Date: Thu, 7 Sep 2017 18:14:50 -0700 Subject: [PATCH 4/7] feedback --- docs/core/rid-catalog.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/core/rid-catalog.md b/docs/core/rid-catalog.md index 94bdb00b8d2fa..1d26664032033 100644 --- a/docs/core/rid-catalog.md +++ b/docs/core/rid-catalog.md @@ -10,7 +10,7 @@ ms.prod: .net-core # .NET Core RID Catalog RID is short for *Runtime IDentifier*. RID values are used to identify target platforms where the application runs. -They're used by .NET packages to represent runtime-specific assets in NuGet packages. The following values are examples of RIDs: `linux-x64`, `ubuntu.14.04-x64`, `win7-x64`, or `osx.10.11-x64`. +They're used by .NET packages to represent platform-specific assets in NuGet packages. The following values are examples of RIDs: `linux-x64`, `ubuntu.14.04-x64`, `win7-x64`, or `osx.10.11-x64`. For the packages with native dependencies, the RID designates on which platforms the package can be restored. RIDs can be set in the `` element of your project file. They're also used via the `--runtime` option with the following [.NET Core CLI commands](./tools/index.md): @@ -45,12 +45,12 @@ If an exact match is not found, NuGet walks back the graph until it finds the cl The following example is the actual entry for the `osx.10.11-x64` RID: ```json -"osx.10.11-x64": { - "#import": [ "osx.10.11", "osx.10.10-x64" ] +"osx.10.12-x64": { + "#import": [ "osx.10.12", "osx.10.11-x64" ] } ``` -The above RID specifies that `osx.10.11-x64` imports `osx.10.10-x64`. So, when NuGet restores packages, it tries to find an exact match for `osx.10.11-x64` in the package. If NuGet cannot find the specific runtime, it can restore packages that specify `osx.10.10-x64` runtimes, for example. +The above RID specifies that `osx.10.12-x64` imports `osx.10.11-x64`. So, when NuGet restores packages, it tries to find an exact match for `osx.10.12-x64` in the package. If NuGet cannot find the specific runtime, it can restore packages that specify `osx.10.11-x64` runtimes, for example. The following example shows a slightly bigger RID graph also defined in the *runtime.json* file: From 9a23e549b5590f9439ab42f48cde0ae99ac9e358 Mon Sep 17 00:00:00 2001 From: Maira Wenzel Date: Thu, 7 Sep 2017 18:15:18 -0700 Subject: [PATCH 5/7] fixed rid value --- docs/core/rid-catalog.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/core/rid-catalog.md b/docs/core/rid-catalog.md index 1d26664032033..d561e79a9f34a 100644 --- a/docs/core/rid-catalog.md +++ b/docs/core/rid-catalog.md @@ -42,7 +42,7 @@ The RID graph or runtime fallback graph is a list of RIDs that are compatible wi When NuGet restores packages, it tries to find an exact match for the specified runtime. If an exact match is not found, NuGet walks back the graph until it finds the closest compatible system according to the RID graph. -The following example is the actual entry for the `osx.10.11-x64` RID: +The following example is the actual entry for the `osx.10.12-x64` RID: ```json "osx.10.12-x64": { From e2d3145b1bf7bb59a8d1253031f78291863fb08a Mon Sep 17 00:00:00 2001 From: Maira Wenzel Date: Thu, 7 Sep 2017 22:49:50 -0700 Subject: [PATCH 6/7] removed unsupported os versions --- docs/core/rid-catalog.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/core/rid-catalog.md b/docs/core/rid-catalog.md index d561e79a9f34a..b9e2fd9933b33 100644 --- a/docs/core/rid-catalog.md +++ b/docs/core/rid-catalog.md @@ -118,7 +118,6 @@ The following list shows the most common RIDs used for each OS. It doesn't cover - `debian.8-x64` - Fedora - `fedora-x64` - - `fedora.23-x64` - `fedora.24-x64` - `fedora.25-x64` (.NET Core 2.0 or later versions) - `fedora.26-x64` (.NET Core 2.0 or later versions) @@ -126,7 +125,6 @@ The following list shows the most common RIDs used for each OS. It doesn't cover - `gentoo-x64` - openSUSE - `opensuse-x64` - - `opensuse.13.2-x64` - `opensuse.42.1-x64` - Oracle Linux - `ol-x64` From c14774cc3efe8873ccc9ada15b0cd8472c35a199 Mon Sep 17 00:00:00 2001 From: Maira Wenzel Date: Thu, 7 Sep 2017 22:52:31 -0700 Subject: [PATCH 7/7] feedback --- docs/core/rid-catalog.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/core/rid-catalog.md b/docs/core/rid-catalog.md index b9e2fd9933b33..8a933d08fdfb0 100644 --- a/docs/core/rid-catalog.md +++ b/docs/core/rid-catalog.md @@ -10,7 +10,7 @@ ms.prod: .net-core # .NET Core RID Catalog RID is short for *Runtime IDentifier*. RID values are used to identify target platforms where the application runs. -They're used by .NET packages to represent platform-specific assets in NuGet packages. The following values are examples of RIDs: `linux-x64`, `ubuntu.14.04-x64`, `win7-x64`, or `osx.10.11-x64`. +They're used by .NET packages to represent platform-specific assets in NuGet packages. The following values are examples of RIDs: `linux-x64`, `ubuntu.14.04-x64`, `win7-x64`, or `osx.10.12-x64`. For the packages with native dependencies, the RID designates on which platforms the package can be restored. RIDs can be set in the `` element of your project file. They're also used via the `--runtime` option with the following [.NET Core CLI commands](./tools/index.md):