Validation Fundamentals
The customer intake form introduces Validating, Validated, e.Cancel, AutoValidate, a working Cancel button and the ValidateChildren() save guard.
This folder is the complete application at this point in the course, with its own solution and port.
Run it
Requirements: .NET 10 SDK and NuGet access to Wisej-4 4.1.0. Use a Wisej development license or trial
as required by your installation. No database setup or external service is needed.
cd "Validation in Wisej.NET Course/Module 1/ValidationClinic"
dotnet run -f net10.0 --urls http://localhost:5901
Open http://localhost:5901. In Visual Studio, open ValidationClinic.slnx and press F5.
The project targets both net10.0-windows and net10.0, so the CLI needs -f when running.
What to try
| Action | Expected result |
|---|---|
| Open customer intake; enter a name but leave email untouched; Save | The untouched email is checked, an error appears, and the repository write count stays at zero. |
| Type an @-less email and leave the field | An error is shown; focus may move because this sample chooses EnableAllowFocusChange. Save still refuses. |
| Type a padded name and leave it | Validated trims only accepted text; it never writes to the repository. |
| Cancel while name is invalid | The dialog closes and the repository remains unchanged. |
| Load valid values, choose Fail next write, then Save | A friendly system message appears; the write count does not change. Save again to recover with the same input. |
| Discard grid edits | Restores the last saved snapshot. Working-copy edits are not persisted automatically. |
The repository starts with Ada Lovelace and Grace Hopper. Every browser session owns its own repository. Its data disappears when the session ends or the app restarts. The live trace shows which validation stage ran; the write count provides visible evidence that rejected input never called a successful write.
Design notes
Module note records the API choices and failure behavior.
The sample uses AutoValidate.EnableAllowFocusChange: errors remain visible while the user reaches another
field to fix a related value. Cancel never causes validation. Save explicitly validates every relevant layer.
The in-memory repository is deliberately a storage stand-in; callers own validation, as in the lesson.
It checks name uniqueness and swaps the saved snapshot only after all repository checks pass.