Integrating win 32 component is already possible in WPF 4.0, even in WPF 3.5 but there is the well-know issue : airspace problems. Each render technology belongs to only one airspace only. So when you place Win32 components in your WPF application they behave as black hole for input, render transformation are not (well) applied, etc. With this 4.5 release, the WPF team solves this drawback. In this post more explanation and an example of how it improves developers’ life will be gived. This post is a part of a serie on WPF 4.5 new features.