March 2010
Intermediate to advanced
1216 pages
33h 44m
English
In some cases the clean window-by-window separation isn't suitable. For example, you might want to place WPF content in an existing form alongside Windows Form content. Although this model is conceptually messier, WPF handles it quite gracefully.
In fact, including Windows Forms content in a WPF application (or vice versa) is more straightforward than adding ActiveX content to a Windows Forms application. In the latter scenario, Visual Studio must generate a wrapper class that sits between the ActiveX control and your code, which manages the transition from managed to unmanaged code. This wrapper is component-specific, which means each ActiveX control you use requires a separate customized wrapper. And ...
Read now
Unlock full access