We too are evaluating docking windows and require this behaviour. We are in fact adding a docking window to a tabbed Mdi child window and had exactly the same exception thrown.
The fix you give does work – thank you, but I am a little concerned (being in the evaluation stage!) by the “use at your own risk” bit. I understand that at the time of writing, the solution had probably not been fully tested etc. Are you likely to be in a position to “guarantee” the solution eventually?
Other suppliers do provide this functionality which require no special incantations but I suspect they do exactly what you recommend behind the scenes as it is apparenlty non-standard functionality – taking Visual Studio as the standard.
Imported from legacy forums. Posted by Nigel (had 447 views)