Programmatic Validation and ErrorProvider Feedback

Validation in Wisej.NETModule 2The lesson guide, the walkthrough video, the knowledge check and the hands-on lab this sample was built from are on learnwisej.com — free, with an AI tutor in every lesson.

Open the course

The intake form adds pure FieldValidation results, one ErrorProvider, per-field clearing, a visible summary and an InvalidMessage comparison on the customer code. This folder is the complete application at this point in the course, with its own solution and port.

The source of this sample

iceteagroup/LearnWisej-SamplesValidation in Wisej.NET Course/Module 2

Browse this folder on GitHub

Or clone it: git clone https://github.com/iceteagroup/LearnWisej-Samples.git — then open ValidationClinic.slnx in Visual Studio and press F5.

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 2/ValidationClinic"
dotnet run -f net10.0 --urls http://localhost:5902

Open http://localhost:5902. 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
Load invalid values, then Save	Name, email and phone problems appear in the summary and beside their fields.
Correct email and Tab	Only the email message disappears; the remaining problems stay visible.
Leave customer code as X and leave its field	The editor shows InvalidMessage, with no provider icon for that field; the summary includes it explicitly.
Load valid values; Save	All field messages clear and the summary hides.
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.