Chapter 7. Known issues

.NET Core SDK 2.1.3xx contains an incorrect NETStandard.Library version. Using this SDK version may result in build failures. To correct this issue, update to SDK 2.1.402 (or later). To update to the latest SDK version, install the latest .NET Core software. To install the latest software, see Installing .NET Core 2.1.

If there is a global.json file that specifies the SDK version and you do not want to update to the latest SDK version, you can work around this issue by removing the following entry in the csproj file.

<TreatWarningsAsErrors>true</TreatWarningsAsErrors>

<TreatWarningsAsErrors>true</TreatWarningsAsErrors>

Global tools that are preinstalled with Microsoft SDK are not available by default on RHEL. The dev-certs, ef, sql-cache, user-secrets, and watch commands are available by default with the Microsoft SDK. On RHEL, these tools can be installed from nuget.org using the dotnet tool install --global <tool> --version '2.1.*' command. When a tool is not installed, the CLI prints the command to install it, for example, dotnet tool install --global dotnet-ef. Note that the version flag --version '2.1.*' should be used to work around the following known issue.

The Microsoft SDK always installs the latest version of a tool. When the latest tool version is not compatible with the installed runtimes, the installation will fail. To install the tool, you must specify an older version that is compatible with .NET Core 2.1 using the --version option. The versions can be found at nuget.org. The 2.2.x tool versions preinstalled with the Microsoft SDK are not compatible with .NET Core 2.1. To install them for .NET Core 2.1, add --version '2.1.*' as shown in the example in the previous paragraph. This issue is being tracked on GitHub.

dotnet dev-certs https --trust does not work on RHEL.

.NET Core supports the creation of HTTPS certificate through dotnet dev-certs https, but it does not support trusting them through dotnet dev-certs https --trust. The client that connects to the ASP.NET Core application, such as curl or firefox, will warn about the untrusted self-signed certificate. To work around this in a browser such as Firefox, ignore the warning and trust the certificate explicitly when the warning about the untrusted certificate comes up. Command-line tools support flags to ignore untrusted certificate. For curl, use --insecure. For wget, use --no-check-certificate.

There are different values for math libraries on different platforms.

Math libraries that are part of .NET Core 2.1 can return different values on different platforms. This is expected behavior. .NET Core 2.1 takes advantage of the platform-specific libraries to improve performance and reduce overhead. See the Math.Cos(double.MaxValue) returns different values on Windows and other platforms issue discussion for more information.

The following issues affected the previous release of .NET Core on RHEL and were fixed by updates.