Added dev-certs related known issue for 5.0 Preview 4
This commit is contained in:
parent
8af40f46c6
commit
bb6b231459
|
@ -16,6 +16,14 @@ This document lists known issues for **.NET 5 Preview 1 and beyond releases** wh
|
|||
|
||||
1. The Microsoft.Windows.Compatibility package references dependencies that are not available at the targeted versions. To workaround, individually reference the packages your project needs. It is tracked by [dotnet/runtime/issues #34351](https://github.com/dotnet/runtime/issues/34351)
|
||||
|
||||
|
||||
## ASP.NET Core Runtime
|
||||
|
||||
### 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)
|
||||
|
||||
## .NET SDK
|
||||
|
||||
### Preview 1
|
||||
|
|
Loading…
Reference in a new issue