Surface cert trust in Blazor debug topic (#18562)

pull/18564/head
Luke Latham 2020-05-29 07:21:26 -05:00 committed by GitHub
parent 640561af26
commit e3ca808345
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 3 deletions

View File

@ -5,7 +5,7 @@ description: Learn how to debug Blazor apps.
monikerRange: '>= aspnetcore-3.1'
ms.author: riande
ms.custom: mvc
ms.date: 05/28/2020
ms.date: 05/29/2020
no-loc: [Blazor, "Identity", "Let's Encrypt", Razor, SignalR]
uid: blazor/debug
---
@ -138,6 +138,7 @@ Browser source maps allow the browser to map compiled files back to their origin
## Troubleshoot
If you're running into errors, the following tip may help:
If you're running into errors, the following tips may help:
In the **Debugger** tab, open the developer tools in your browser. In the console, execute `localStorage.clear()` to remove any breakpoints.
* In the **Debugger** tab, open the developer tools in your browser. In the console, execute `localStorage.clear()` to remove any breakpoints.
* Confirm that you've installed and trusted the ASP.NET Core HTTPS development certificate. For more information, see <xref:security/enforcing-ssl#troubleshoot-certificate-problems>.