FrameworkContentElement Class (System.Windows)

.NET Framework Class Library

FrameworkContentElement Class

Updated: July 2008

FrameworkContentElement is the WPF framework-level implementation and expansion of the ContentElement base class. FrameworkContentElement adds support for additional input APIs (including tooltips and context menus), storyboards, data context for data binding, styles support, and logical tree helper APIs.

Namespace: System.Windows
Assembly: PresentationFramework (in PresentationFramework.dll)
XMLNS for XAML: http://schemas.microsoft.com/winfx/2006/xaml/presentation, http://schemas.microsoft.com/netfx/2007/xaml/presentation

Syntax

Visual Basic (Declaration)

<RuntimeNamePropertyAttribute("Name")> _
<XmlLangPropertyAttribute("Language")> _
<StyleTypedPropertyAttribute(Property := "FocusVisualStyle", StyleTargetType := GetType(Control))> _
Public Class FrameworkContentElement _
    Inherits ContentElement _
    Implements IFrameworkInputElement, IInputElement, ISupportInitialize

Visual Basic (Usage)

Dim instance As FrameworkContentElement

[RuntimeNamePropertyAttribute("Name")]
[XmlLangPropertyAttribute("Language")]
[StyleTypedPropertyAttribute(Property = "FocusVisualStyle", StyleTargetType = typeof(Control))]
public class FrameworkContentElement : ContentElement, 
    IFrameworkInputElement, IInputElement, ISupportInitialize

Visual C++

[RuntimeNamePropertyAttribute(L"Name")]
[XmlLangPropertyAttribute(L"Language")]
[StyleTypedPropertyAttribute(Property = L"FocusVisualStyle", StyleTargetType = typeof(Control))]
public ref class FrameworkContentElement : public ContentElement, 
    IFrameworkInputElement, IInputElement, ISupportInitialize

JScript

public class FrameworkContentElement extends ContentElement implements IFrameworkInputElement, IInputElement, ISupportInitialize

XAML Object Element Usage

<FrameworkContentElement .../>

Remarks

FrameworkContentElement does not yet define its own rendering behavior; instantiating an actual FrameworkContentElement class instance in code or markup is possible but displays nothing in a WPF application user interface (UI). Rendering logic must be provided by classes that take FrameworkContentElement child elements as part of their content model, or in FrameworkContentElement derived classes.

FrameworkContentElement deliberately parallels many of the same APIs as FrameworkElement. Note that certain APIs found on FrameworkElement will not have a FrameworkContentElement equivalent. Several of the FrameworkElement APIs are for functionality such as geometry representation or layout, which are not relevant for a FrameworkContentElement.

The majority of existing FrameworkContentElement derived classes will be found in the System.Windows.Documents namespace. Many of these derived classes implement elements for the flow document model. Certain derived classes such as Hyperlink have some control-like functionality, but are derived from FrameworkContentElement such that the control-like elements can still participate in the flow document model.

Inheritance Hierarchy

System..::.Object
  System.Windows.Threading..::.DispatcherObject
    System.Windows..::.DependencyObject
      System.Windows..::.ContentElement
        System.Windows..::.FrameworkContentElement
          System.Windows.Controls..::.DefinitionBase
          System.Windows.Documents..::.FixedDocument
          System.Windows.Documents..::.FixedDocumentSequence
          System.Windows.Documents..::.FlowDocument
          System.Windows.Documents..::.TableColumn
          System.Windows.Documents..::.TextElement

Thread Safety

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Platforms

Windows 7, Windows Vista, Windows XP SP2, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003

The .NET Framework and .NET Compact Framework do not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

Version Information