Verification and Exception Handling in MVC and manual activation Verification

Whether you get a model through the action parameter, or manually calling updatemodel () or tryupdatemodel (), the default defaultmodelbinder will automatically perform legal verification. However, when you use other methods to update the model, automatic verification will be skipped. For example:

Public actionresult makebooking (string clientname, datetime? Appointmentdate,

Bool acceptsterms)

{

VaR APPT = new appointment {

Clientname = clientname,

Appointmentdate = appointmentdate. getvalueordefault ()

};

If (! Acceptsterms)

Modelstate. addmodelerror ("acceptsterms", "you must accept the terms ");

If (modelstate. isvalid ){

// To do: actually save the appointment to the database or whatever

// Bypass Verification

Return view ("completed", APPT );

}

Else

Return view (); // re-renders the same view so the user can fix the errors

}

The controller base class provides two basic methods for us to manually trigger verification.

• Validatemodel () verification. If it is invalid, an error will be registered and an invalidoperationexception will be thrown.

.

• The difference between tryvalidatemodel () and validatemodel is that it does not throw an exception, but returns the same value as modestate. isvalide.

Whether you get a model through the action parameter, or manually calling updatemodel () or tryupdatemodel (), the default defaultmodelbinder will automatically perform legal verification. However, when you use other methods to update the model, automatic verification will be skipped. For example:

Public actionresult makebooking (string clientname, datetime? Appointmentdate,

Bool acceptsterms)

{

VaR APPT = new appointment {

Clientname = clientname,

Appointmentdate = appointmentdate. getvalueordefault ()

};

If (! Acceptsterms)

Modelstate. addmodelerror ("acceptsterms", "you must accept the terms ");

If (modelstate. isvalid ){

// To do: actually save the appointment to the database or whatever

// Bypass Verification

Return view ("completed", APPT );

}

Else

Return view (); // re-renders the same view so the user can fix the errors

}

The controller base class provides two basic methods for us to manually trigger verification.

• Validatemodel () verification. If it is invalid, an error will be registered and an invalidoperationexception will be thrown.

.

• The difference between tryvalidatemodel () and validatemodel is that it does not throw an exception, but returns the same value as modestate. isvalide.