Fedora Account System
Red Hat Associate
Red Hat Customer
.NET Core 1.0.4 was released upstream: We need to update our .NET Core 1.0.x package to the latest release, 1.0.4. One major divergence from upstream is that we will not be migrating the new tooling. Our tooling will stick to project.json and not support the new csproj format. This means that our 1.0.4 release should be an entirely backwards compatible update unlike the version released upstream.
[tester@rhel7-x64 ~]$ rpm -qa | grep dotnet rh-dotnetcore10-1.0-4.el7.x86_64 rh-dotnetcore10-libuv-1.9.0-1.el7.x86_64 rh-dotnetcore10-dotnetcore-1.0.4-1.el7.x86_64 rh-dotnetcore10-runtime-1.0-4.el7.x86_64 rh-dotnetcore10-libcurl-7.47.1-4.el7.x86_64 [tester@rhel7-x64 ~]$ scl enable rh-dotnetcore10 -- dotnet --version 1.0.0-preview2-003157 [tester@rhel7-x64 ~]$ scl enable rh-dotnetcore10 -- dotnet Microsoft .NET Core Shared Framework Host Version : 1.0.1 Build : 4c41eace622faf3cdfdd0bcd4030a71235fbd3d5 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 .NET SDK from: http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409 The 1.0.1 iv core version appeared also last time, so I guess it is correct. Still pinging devs.
As https://bugzilla.redhat.com/show_bug.cgi?id=1424492 have passed, this seems to be really 1.0.4
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-0519.html