Implement a new WPF interoperability control

Describe the bug It seems that, when moving from 11.0.0-preview8 to 11.0.0-rc1.1, the Avalonia.Interoperability project was changed and, in that change, the WinForms folder was moved but the Wpf folder was fully removed. I don’t know if there was a plan to add it back later or something but we would GREATLY benefit from the Wpf interop, it makes migating apps to Avalonia sooooo much easier as we can do it piecemeal.

To Reproduce Steps to reproduce the behavior:

1. checkout release 11.0.0-rc1.1

Expected behavior A clear and concise description of what you expected to happen.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Version 11.0.0-rc1.1

Additional context Add any other context about the problem here.

[timunie]

@heuristicAL docs are under heavy development for v11 atm. So maybe after the docs for v11 are alive, you can file a PR if still needed. Here is the 0.10.x docs:

https://github.com/AvaloniaUI/Documentation

[heuristicAL]

Oh, that’s totally acceptable! Thanks again for the info! I’ll keep tracking this task in case the feature is released in the future but, in the meantime, HwndHost seems like a perfectly acceptable alternative. Y’all should add it to the docs! It’s hard to find any info about this. I can look into contributing it myself if someone can point me to which section it should be in 😃