From 9a55403db9a7b3f7f9d536ea99e50eba59ddc44e Mon Sep 17 00:00:00 2001 From: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com> Date: Wed, 12 May 2021 06:07:14 +1000 Subject: [PATCH] Update 31-to-50.md (#22258) * Update 31-to-50.md * Apply suggestions from code review Co-authored-by: Luke Latham <1622880+guardrex@users.noreply.github.com> Co-authored-by: Luke Latham <1622880+guardrex@users.noreply.github.com> --- aspnetcore/migration/31-to-50.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/aspnetcore/migration/31-to-50.md b/aspnetcore/migration/31-to-50.md index 572689804d..9379ab24e9 100644 --- a/aspnetcore/migration/31-to-50.md +++ b/aspnetcore/migration/31-to-50.md @@ -58,6 +58,10 @@ If updating a Blazor WebAssembly project, skip to the [Update Blazor WebAssembly ``` +## Delete `bin` and `obj` folders + +You may need to delete the `bin` and `obj` folders. Run `dotnet nuget locals --clear all` to clear the NuGet package cache. + ## Changes to Blazor app routing logic in 5.0.1 and further 5.x releases up to 6.0 The computation of route precedence changed in the ASP.NET Core 5.0.1 patch release. This might affect you if you've defined catch-all routes or routes with optional parameters.