From 40f282b00bc25b11720cd3928e2f60a401ea6002 Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Wed, 27 May 2020 19:32:38 -0500 Subject: [PATCH] Add a Troubleshoot section to Blazor forms topic (#18521) --- aspnetcore/blazor/forms-validation.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/aspnetcore/blazor/forms-validation.md b/aspnetcore/blazor/forms-validation.md index 7dbe49a214..ec8f174fe2 100644 --- a/aspnetcore/blazor/forms-validation.md +++ b/aspnetcore/blazor/forms-validation.md @@ -5,7 +5,7 @@ description: Learn how to use forms and field validation scenarios in Blazor. monikerRange: '>= aspnetcore-3.1' ms.author: riande ms.custom: mvc -ms.date: 03/17/2020 +ms.date: 05/27/2020 no-loc: [Blazor, "Identity", "Let's Encrypt", Razor, SignalR] uid: blazor/forms-validation --- @@ -521,3 +521,15 @@ A side effect of the preceding approach is that a InvalidOperationException: EditForm requires a Model parameter, or an EditContext parameter, but not both. + +Confirm that the has a or . + +When assigning a to the form, confirm that the model type is instantiated, as the following example shows: + +```csharp +private ExampleModel exampleModel = new ExampleModel(); +```