maxmustermann/dotnet-core
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update 5.0-known-issues.md

Browse source
This commit is contained in:
Artak 2020-05-12 12:56:21 -07:00 committed by GitHub
parent bb6b231459
commit f3e7c77327
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
release-notes/5.0/5.0-known-issues.md
View file

@ -21,8 +21,12 @@ This document lists known issues for **.NET 5 Preview 1 and beyond releases** wh
### Preview 4
1. The dotnet-certs tool will corrup the dev-certificate if run in any Docker-enabled scenario. If you create / load any docker-enabled ASP.NET Core project the tool will run automatically to check for a valid certificate, won't find it and will try to recreate it. As a result, it'll leave the certificate in a corrupted state.
We recommend to create / open any docker-enabled projects while on Preview 4 SDK. This will be fixed in Preview 5. It is tracked by [dotnet/aspnetcore/issues #21733](https://github.com/dotnet/aspnetcore/issues/21733)
1. When running a docker enabled application from Visual Studio or running `dotnet dev-certs https --trust -ep <<path.pfx>> -p <<password>>` the HTTPS certificate created by ASP.NET Core will become corrupted and will prevent applications from running.
If you try to run the `dotnet dev-certs` tool again it will think that there is no valid certificate and will try to recreate a new one every time it runs. To avoid this situation, you can add a global.json file at the root of your project and set it to use the latest 3.1.xxx installed sdk.
If you tried to run the application within Visual Studio and it corrupted the certificate you will have to clean the existing certificates from your certificate store using the windows tooling. To do that, open the certificate manager (Windows+R -> mmc -> File -> Add remote add-in -> Certificates -> Current user -> Personal) and delete all the certificates that contain the "ASP.NET Core HTTPS development certificate" ![image](https://user-images.githubusercontent.com/6995051/81736370-4d62cc80-944b-11ea-9a72-d7c031d62bf5.png) and also remove them from Trusted Root Certification Authorities
We recommend to not create / open any docker-enabled projects while on Preview 4 SDK.
This will be fixed in the Preview 5 release. It is tracked by [dotnet/aspnetcore/issues #21733](https://github.com/dotnet/aspnetcore/issues/21733)
## .NET SDK