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.
Queries for whether a specified property should be treated as ambient in the current scope.
public interface class IQueryAmbient
public interface IQueryAmbient
type IQueryAmbient = interface
Public Interface IQueryAmbient
The purpose of an ambient property mechanism is to improve parsing time by informing a XAML object writer to avoid instantiating certain objects, in cases where it is known that the objects are for values that are temporary and not useful for a typical run time application. Normally, XAML lookups or XAML processing of a property get accessor would need to instantiate such objects to fill the object graph representation with ready-to-use values.
IQueryAmbient is a parallel mechanism to AmbientAttribute. IQueryAmbient is the specialized mechanism that avoids using reflection to determine information, and can also act situationally (a given object could choose to report
false for IsAmbientPropertyAvailable), whereas the attribute is essentially static analysis). AmbientAttribute is the general mechanism that can be used by XAML object writers and that typically correlates to the dedicated XAML type system properties IsAmbient and IsAmbient.
WPF Implementations of IQueryAmbient
In WPF, IQueryAmbient is used for the resource dictionary lookup process. The lookup process gets successive
Resources values throughout the WPF logical tree, working towards the root of the resource scope until either a key is found or the key is determined to not exist in scope. Normally, doing so would require instantiating a ResourceDictionary each time to receive the results. Declaring the contents of
Resources as ambient so long as
Resources exists optimizes this lookup process. In WPF, this interface is implemented in the following cases:
FrameworkElement implements IQueryAmbient.IsAmbientPropertyAvailable to return
truefor all property names if it contains an existing ResourceDictionary for Resources, and so long as the query is not for the Resources property itself.
In each of these cases, the relevant
Resourcesproperty (and Template) are attributed as AmbientAttribute. The typical usage is to query for the properties that are NOT the AmbientAttribute attributed properties of the object that defines the interface. In other words, so long as a resource dictionary exists in order to provide the potential run time value when the object graph is created, any other property besides the resource dictionary's property container can be treated as ambient.
Queries for whether a specified named property can be considered ambient in the current scope.