---
title: MethodValidator
summary: API reference for MethodValidator.
status: draft
owner: SAIF documentation team
last_reviewed: 2026-08-17
library: SAIF.Presentation.Web.Binding.Infragistics103
reference_type: embedded
---

# MethodValidator

This declared delegate represents a method-style validation callback that would receive a bound object and an error collection, suggesting an earlier or alternate design for custom validation dispatch. In the current compiled validator flow, the method-mode implementation is wired to a `CustomValidator` function delegate instead, so this type documents the declared contract while flagging the runtime usage gap that readers must account for.

## Purpose

- Captures the library's declared subroutine-style signature for method-level custom validation callbacks.
- Highlights the difference between the declared delegate surface and the method-mode dispatch path currently implemented by `clsCustomValidator`.*


## Context

- Namespace: `SAIF.Presentation.Web.Binding`
- Assembly/package: `SAIF.Presentation.Web.Binding.Infragistics103` (embedded/bundled as source, not independently packaged)

## Public members

| Member | Signature | Purpose |
| --- | --- | --- |
| MethodValidator | `Public Delegate Sub MethodValidator(ByRef target As Object, ByRef inErrors As ArrayList)` | Declared callback signature for method-level validation, passing the bound object and a caller-populated error collection; intended usage as the method-mode contract is inferred because the active `clsCustomValidator` implementation invokes `CustomValidator` instead of this delegate type.* |


## Behavioral notes

- The signature itself is verified in `Enums.vb`.
- Commented-out `clsObjectBindManager.AddCustomValidator` overloads and the delegate name suggest this type was meant for method-mode validation registration, but the active compiled path uses `CustomValidator` and returns a Boolean instead.*


## Constraints and usage notes

- Treat this delegate as declared API surface rather than confirmed active runtime behavior until method-mode wiring is revised or separately validated in consuming code.*
- New code following the current manager implementation should use the active `CustomValidator`-based method registration path.

> **Note:** Statements marked with * were inferred from code structure, naming
> conventions, or contextual evidence where direct confirmation was not available
> in source artifacts.

## Sources

- `SAIF.Presentation.Web.Binding.Infragistics103\Enums.vb`
- `SAIF.Presentation.Web.Binding.Infragistics103\clsCustomValidator.vb`
- `SAIF.Presentation.Web.Binding.Infragistics103\clsObjectBindManager.vb`