| IdeaBlade.Validation Assembly > IdeaBlade.Validation Namespace > VerifierOptions Class : ExecutionModes Property |
'Declaration<DataMemberAttribute()> Public Property ExecutionModes As VerifierExecutionModes
'UsageDim instance As VerifierOptions Dim value As VerifierExecutionModes instance.ExecutionModes = value value = instance.ExecutionModes
[DataMember()] public VerifierExecutionModes ExecutionModes {get; set;}
An example of the first would be if we wanted to verify that an instance of an Employee object was completely valid before we save it and in this case we might want to perform a large number of verifications on a number of individual properties of the employee object in order to completely verify its correctness. An example of the second is when we are either in the process of changing or have changed the “HireDate” on an employee and we only want to perform those verifications that are in some way effected by this change. The latter is an example of a “Triggered” verification and the first is an example of an “Instance” verification.
“Triggered” verifications can be further subdivided into “pre” and “post” triggering categories. A “BeforeSet” trigger verification is one that should be applied before some specific change is actually made and a “AfterSet” trigger verification is one where we want to execute the verification immediately after some change has occurred. Any given verifier might be written in such a way as to be applicable under several of these conditions.
The default is VerifierExecutionModes.InstanceAndOnBeforeSetTriggers.
Target Platforms: Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2