I'm following your vs project "Validation Example - Selfservicing" to setup my own validation project (using dependency injection).

Your "ValidateEntityBeforeSave" function in the file OrderValidator.cs in the project "SD.LLBLGen.Pro.Examples.Validators" does not call base.ValidateEntityBeforeSave(involvedEntity); at the end of the function.

Why?

Shouldn't all override validators call the function in the base class?

This is done in the other example (CustomerValidator.cs)

Maybe it should call the base method. The base class however didn't implement that as the ValidatorBase is intended to facilitate things, but calling base.ValidateEntityBeforeSave does nothing actually.

daelmo wrote:

Maybe it should call the base method. The base class however didn't implement that as the ValidatorBase is intended to facilitate things, but calling base.ValidateEntityBeforeSave does nothing actually.

Hi David. Thx for your reply.

How does the validator classes function when doing save, delete and update multi operations?

morten71 wrote:

How does the validator classes function when doing save, delete and update multi operations?

This is explained in detail in the docs. Basically, if you do something like:

adapter.SaveEntityCollection(myCollection);

then each entity inside the entity passes through yourValidator.ValidateEntityBeforeSave and yourValidator.ValidateEntityAfterSave. Similar with adapter.DeleteEntityCollection(myCollection) and yourValidator.ValidateEntityBeforeDelete.

Now, if you do something like:

adapter.ValidateEntityBeforeDelete(newValues, filter);

... it's different, as you are not working with entities, but with a set of new values and a filter. In that case you should write your validation in your own business logic. You should establish what you want to validate and how. In most cases you could do that just using the filter.