.NET Core 1.1.1 was released upstream. We need to update our version of .NET Core to this latest release as well. Unlike the version release upstream, our builds of .NET Core 1.1.1 will continue using the older tooling. They will support building projects using project.json and not support the new csproj format. This means our release of 1.1.1 will be backwards compatible and not break the workflow for anyone using the previous versions of the tooling.
[tester@rhel7-x64 ~]$ rpm -qa | grep dotnet rh-dotnetcore11-1.0-1.el7.x86_64 rh-dotnetcore11-libuv-1.9.0-1.el7.x86_64 rh-dotnetcore11-dotnetcore-1.1.1-1.el7.x86_64 rh-dotnetcore11-libcurl-7.47.1-4.el7.x86_64 rh-dotnetcore11-runtime-1.0-1.el7.x86_64 [tester@rhel7-x64 ~]$ scl enable rh-dotnetcore11 -- dotnet --version 1.0.0-preview2-1-003176 [tester@rhel7-x64 ~]$ scl enable rh-dotnetcore11 -- dotnet Microsoft .NET Core Shared Framework Host Version : 1.1.0 Build : 362e48a95c86b40cd1f2ef3d08741f7fed897956 Usage: dotnet [common-options] [[options] path-to-application] Common Options: --help Display .NET Core Shared Framework Host help. --version Display .NET Core Shared Framework Host version. Options: --fx-version <version> Version of the installed Shared Framework to use to run the application. --additionalprobingpath <path> Path containing probing policy and assemblies to probe for. Path to Application: The path to a .NET Core managed application, dll or exe file to execute. If you are debugging the Shared Framework Host, set 'COREHOST_TRACE' to '1' in your environment. To get started on developing applications for .NET Core, install the SDK from: http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409 [tester@rhel7-x64 ~]$ Looks like 1.1 core is used
(In reply to jiri vanek from comment #3) > [tester@rhel7-x64 ~]$ scl enable rh-dotnetcore11 -- dotnet > > Microsoft .NET Core Shared Framework Host > > Version : 1.1.0 > Build : 362e48a95c86b40cd1f2ef3d08741f7fed897956 > Looks like 1.1 core is used I asked Microsoft about this when they shared their sources with me. It's very non-obvious so here's my understanding of version numbers. This 1.1.0 is the version of the `dotnet` command, which is also known as the shared-host and basically is the version of https://github.com/dotnet/core-setup. The version of core-setup didn't change because there were no fixes to it. dotnet --version gives the version of cli (https://github.com/dotnet/cli) which is just a build-version bump from the version in what we called ".NET Core 1.1.0". The bugfixes in this update were in CoreCLR and CoreFX. There's no simple way to print the version string for that. I use ls $(dirname $(readlink -f $(scl enable rh-dotnetcore11 -- which dotnet)))/shared/Microsoft.NETCore.App Which shows this is 1.1.1.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0520.html