Chapter 7. Known issues

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

.NET supports the creation of HTTPS certificates 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 certificates. For curl, use the --insecure flag. For wget, use the --no-check-certificate flag.

There are no NuGet packages for ppc64le and s390x on nuget.org.

Using the rhel.8-s390x, linux-s390x, rhel.8-ppc64le, or linux-ppc64le runtime identifier can cause some dotnet commands to fail when they try to obtain these packages. These commands are either not fully supported on ppc64le and s390x as described in the other known issues, or the issue can be fixed by not specifying the runtime identifier.

The default version of the Microsoft.NET.Test.Sdk package in the test project templates (xunit, nunit, mstest) is unusable on ppc64le. Trying to build/run tests will fail with a "System.NotSupportedException: Specified method is not supported" exception.

If you are trying to run tests on ppc64le, update the version of the Microsoft.NET.Test.Sdk package to at least 17.4.0.