BindingFailedEventHandler Delegate

Reference

Definition

Namespace:: Windows.UI.Xaml

Important

Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.

Edit

Represents the method that will handle the DebugSettings.BindingFailed event.

public delegate void BindingFailedEventHandler(Platform::Object ^ sender, BindingFailedEventArgs ^ e);

/// [Windows.Foundation.Metadata.ContractVersion(Windows.Foundation.UniversalApiContract, 65536)]
/// [Windows.Foundation.Metadata.Guid(325785474, 21690, 16909, 161, 170, 130, 130, 135, 33, 205, 230)]
class BindingFailedEventHandler : MulticastDelegate

[Windows.Foundation.Metadata.ContractVersion(typeof(Windows.Foundation.UniversalApiContract), 65536)]
[Windows.Foundation.Metadata.Guid(325785474, 21690, 16909, 161, 170, 130, 130, 135, 33, 205, 230)]
public delegate void BindingFailedEventHandler(object sender, BindingFailedEventArgs e);

Public Delegate Sub BindingFailedEventHandler(sender As Object, e As BindingFailedEventArgs)

Parameters

sender: Object
Platform::Object

IInspectable

The source of the event.

e: BindingFailedEventArgs

The event data.

Attributes: ContractVersionAttribute GuidAttribute

Windows requirements

Device family	Windows 10 (introduced in 10.0.10240.0)
API contract	Windows.Foundation.UniversalApiContract (introduced in v1.0)

Remarks

IsBindingTracingEnabled must be true and there must be a debugger attached to the app process in order for BindingFailed to occur 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