Provides markup compile and tools support for named XAML elements and for attaching event handlers to them.
Assembly: System.Xaml (in System.Xaml.dll)
Thetype exposes the following members.
This interface is used internally by Baml2006Reader.
Implementations of InitializeComponent are widely observable as part of the infrastructure provided by frameworks or technologies that use XAML combined with application and programming models. For example, whenever you look at the generated classes for XAML root elements in WPF pages and applications, you will see InitializeComponent defined in the output. That method also exists in the compiled assembly and plays a role in the WPF application model of loading the XAML UI content at XAML parse time. For more information on the WPF integration of the InitializeComponent concept, see Application Management Overview or Code-Behind and XAML in WPF.
In previous versions of the .NET Framework, this interface existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, is in the System.Xaml assembly. . For more information, see Types Migrated from WPF to System.Xaml.
A failure to resolve during an attempted build is often an indicator that you have not updated your WPF project correctly. In particular, the project is not referencing the System.Xaml assembly for a project that targets .NET Framework 4. Try running the devenv /upgrade option for the project, or otherwise adjust the project assembly references so that System.Xaml is in the reference list.
Windows Phone 8.1, Windows Phone 8, Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.