Custom Validation Methods, Services and Rules

Validation in Wisej.NETModule 4The 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

A UI-independent ContactValidator, a MinimumAgeValidationRule and paired start/end date feedback separate field shape from business meaning. 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 4

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

Open http://localhost:5904. 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 valid values; move end date before start date	Both date pickers show the same message; focus can move to either picker to correct it.
Set birth date to tomorrow or less than 18 years ago	The custom age rule rejects it. The shared service repeats the age policy when invoked without a UI.
Use a birth date exactly 18 years ago	The boundary is accepted.
Correct the date order; Save	Both date messages clear; field and business stages pass before the write.
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.