Assembly: PresentationFramework (in presentationframework.dll)
A property path that either describes a path to a common language runtime (CLR) property, or a single dependency property.
This constructor has two completely different usages depending on whether it is being used for a source-mode property path for a binding, or for a target-mode single-step property path for a storyboard target.
If using this PropertyPath in source mode for a binding, parameter is a string representing a property name, or can be a string that describes a "step-through" path to the property in the CLR object model of the object that is being used as the source for a binding. For a binding property path, the character that identifies a "step" is a dot (.). Indexer references (including multiple indexers, and type differentiation) are also supported. For more details on the syntax of the string as specifically used by the Binding object, see Binding.Path. A property used as a binding source need not be a dependency property. If the binding updates two-way, the property referenced must be read-write. Also note that the binding target does have to be a dependency property. For details, see Data Binding Overview.
If using this PropertyPath in target mode for a single-step path for a storyboard target, parameter is generally provided as type DependencyProperty. You can also specify a string that is the Name. Either of these evaluate to the same result, because it is stored internally as a string. A provided DependencyProperty is converted to a string through DependencyPropertyConverter. The DependencyPropertyConverter supports a qualified naming format for dependency properties, so you can specify a typeName.propertyName qualified dependency property name string to the System.Windows.PropertyPath constructor in code. The qualified path to the dependency property identifier is a different concept than a complex path. A complex-path PropertyPath should instead be created with the System.Windows.PropertyPath constructor.
Windows 98, Windows Server 2000 SP4, Windows CE, Windows Millennium Edition, Windows Mobile for Pocket PC, Windows Mobile for Smartphone, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter EditionThe Microsoft .NET Framework 3.0 is supported on Windows Vista, Microsoft Windows XP SP2, and Windows Server 2003 SP1.