With the adoption of WPF often coming as an interop -piece-by-piece- substitution across existing WinForms applications, this perspective would be a good one to focus upon. What are best practices for migrating a WinForms suite to WPF incrementally, mixed, interoperational?
footballism just contributed a tidbit of knowledge regarding use of BindingListCollectionView in ViewModels to help with interop situations, ViewModels, and DataSets...
Other than this, WinForms is going the way of the DoDo bird, imho.
-> What are best practices for migrating a WinForms suite to WPF incrementally, mixed, interoperational?
ElementHost and WindowsFormsHost are the things which you could plug into WPF visual tree or Windows Forms' hwnd parenting tree to enable Windows Forms & WPF interop, but there are many issues when mixing heterogeous content, such as airspace issue, focus interop issue, and Windows Forms/WPF message pump interop issue etc etc.
I've dealt with many such issues, so probably I just look at this from a very buggy mindset:)