ToolWindowContainer and its Reference to DockSite

Hi Rick,

You shouldn't be modifying the ToolWindowContainer.Windows collection as that is something used internally by us and initial XAML load.  Instead, you should be able to use methods like ToolWindow.Attach(IDockTarget) or ToolWindow.Dock(IDockTarget, Side) to programmatically move a ToolWindow.  The IDockTarget can be another open ToolWindow, ToolWindowContainer, Workspace, etc.  But you should never keep references to specify ToolWindowContainer instances since those are dynamically created and destroyed as layout changes occur.  You could get a current ToolWindowContainer reference (its base class actually) for a ToolWindow via ToolWindow.ParentContainer, but it's easier to just target a ToolWindow instead of its container.

I did try Attach() and Dock() with no joy.  Attach only worked for the first move, say from container A to container B, but had no impact when trying to move again from B to A.  Dock didn't seem to do anything at all.  I'll take another stab at it and put together a sample project that illustrates the issues if I can't get it working.

Hi Rick,

That all should be working ok.  We're not aware of any bugs in those methods.  If you do run into something you think might not be working as intended, please let us know how to reproduce it in one of our samples.  Or a new simple sample project of your own is fine too if you want to send that to our ticket system.  Thanks!

I just entered a ticket and included a small sample project that illustrates the issue.

Hi Rick,

Thanks for the sample.  It looks like you are naming ToolWindowContainer instances and targeting those.  That is a no-no since per above, containers are dynamically created and described as layout changes occur.  Only DockSite, DocumentWindow, ToolWindow, Workspace, and TabbedMdiHost objects remain through layout changes and are safe to name and target.  If you change your code to Attach or Dock around ToolWindow instances instead of ToolWindowContainers, it works fine.