DebugSettings.BindingFailed Event

public:
 virtual event BindingFailedEventHandler ^ BindingFailed;

// Register
event_token BindingFailed(BindingFailedEventHandler const& handler) const;

// Revoke with event_token
void BindingFailed(event_token const* cookie) const;

// Revoke with event_revoker
DebugSettings::BindingFailed_revoker BindingFailed(auto_revoke_t, BindingFailedEventHandler const& handler) const;

public event BindingFailedEventHandler BindingFailed;

function onBindingFailed(eventArgs) { /* Your code */ }
debugSettings.addEventListener("bindingfailed", onBindingFailed);
debugSettings.removeEventListener("bindingfailed", onBindingFailed);
- or -
debugSettings.onbindingfailed = onBindingFailed;

Public Custom Event BindingFailed As BindingFailedEventHandler 

Event Type

Remarks

IsBindingTracingEnabled must be true and there must be a debugger attached to the app process in order for BindingFailed to fire and for tracing to appear in debugger output. You don't need to handle the event in order to see tracing appear in a debugger. The debugger output contains message information that goes to the Output window of the debugger. Attaching a BindingFailed handler yourself is an advanced scenario for when you want to see the raw message.

Applies to

See also

• BindingFailedEventHandler
• IsBindingTracingEnabled
• Data binding in depth