From b72409c0f0b284af9c43c5d8f8020d6c97cffb3f Mon Sep 17 00:00:00 2001 From: Axel Date: Mon, 8 Jun 2026 16:27:09 +0200 Subject: [PATCH 1/2] Correct mistake in WOF -> WPF From the context, WOF appears to be a typo and the paragraph makes more sense if WPF is substituted in place of WOF. --- dotnet-desktop-guide/wpf/advanced/xaml-syntax-in-detail.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dotnet-desktop-guide/wpf/advanced/xaml-syntax-in-detail.md b/dotnet-desktop-guide/wpf/advanced/xaml-syntax-in-detail.md index ca3c2d314e..2557de0fe8 100644 --- a/dotnet-desktop-guide/wpf/advanced/xaml-syntax-in-detail.md +++ b/dotnet-desktop-guide/wpf/advanced/xaml-syntax-in-detail.md @@ -303,7 +303,7 @@ Attached properties use a syntax that superficially resembles property element s ## Attached Events -Attached events are another programming concept introduced in XAML where events can be defined by a specific type, but handlers may be attached on any object element. In the WOF implementation, often the type that defines an attached event is a static type that defines a service, and sometimes those attached events are exposed by a routed event alias in types that expose the service. Handlers for attached events are specified through attribute syntax. As with attached events, the attribute syntax is expanded for attached events to allow a *typeName*.*eventName* usage, where *typeName* is the class that provides `Add` and `Remove` event handler accessors for the attached event infrastructure, and *eventName* is the event name. +Attached events are another programming concept introduced in XAML where events can be defined by a specific type, but handlers may be attached on any object element. In the WPF implementation, often the type that defines an attached event is a static type that defines a service, and sometimes those attached events are exposed by a routed event alias in types that expose the service. Handlers for attached events are specified through attribute syntax. As with attached events, the attribute syntax is expanded for attached events to allow a *typeName*.*eventName* usage, where *typeName* is the class that provides `Add` and `Remove` event handler accessors for the attached event infrastructure, and *eventName* is the event name. From 3fa8185ba2261a33da3a6061c82a8f55357824a3 Mon Sep 17 00:00:00 2001 From: "Andy (Steve) De George" <67293991+adegeo@users.noreply.github.com> Date: Thu, 11 Jun 2026 08:23:39 -0700 Subject: [PATCH 2/2] Update xaml-syntax-in-detail.md --- dotnet-desktop-guide/wpf/advanced/xaml-syntax-in-detail.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dotnet-desktop-guide/wpf/advanced/xaml-syntax-in-detail.md b/dotnet-desktop-guide/wpf/advanced/xaml-syntax-in-detail.md index 2557de0fe8..14594abdf0 100644 --- a/dotnet-desktop-guide/wpf/advanced/xaml-syntax-in-detail.md +++ b/dotnet-desktop-guide/wpf/advanced/xaml-syntax-in-detail.md @@ -303,7 +303,7 @@ Attached properties use a syntax that superficially resembles property element s ## Attached Events -Attached events are another programming concept introduced in XAML where events can be defined by a specific type, but handlers may be attached on any object element. In the WPF implementation, often the type that defines an attached event is a static type that defines a service, and sometimes those attached events are exposed by a routed event alias in types that expose the service. Handlers for attached events are specified through attribute syntax. As with attached events, the attribute syntax is expanded for attached events to allow a *typeName*.*eventName* usage, where *typeName* is the class that provides `Add` and `Remove` event handler accessors for the attached event infrastructure, and *eventName* is the event name. +Attached events are another programming concept introduced in XAML where events can be defined by a specific type, but handlers may be attached on any object element. In the WPF implementation, often the type that defines an attached event is a static type that defines a service, and sometimes those attached events are exposed by a routed event alias in types that expose the service. Handlers for attached events are specified through attribute syntax. As with attached properties, the attribute syntax is expanded for attached events to allow a *typeName*.*eventName* usage, where *typeName* is the class that provides `Add` and `Remove` event handler accessors for the attached event infrastructure, and *eventName* is the event name.