Hi Stefan,

This issue is emerging from an Enterprise application and I do not currently have the time/resources to try and recreate the issue on a small scale.

To give you some more information, we are using PRISM and MVVM to build the application. Once a piece of analysis has been visualised on a dashboard i.e. data retrieved and rendered as a chart/grid etc., the visualisation itself is stored in a ViewModel and not recreated when re-accessed by navigating away and then back. When the control is re-bound to display itself again the following code is run to ensure the visual tree can add the control again:

public static void ClearParent(object obj)         {             if (obj == null) return;

            var control = obj as FrameworkElement;

            if (control == null) return;

            var contentPresenter = control.Parent as ContentPresenter;             if (contentPresenter != null)             {                 contentPresenter.Content = null;             }

            var contentControl = control.Parent as ContentControl;             if (contentControl != null)             {                 contentControl.Content = null;             }         }

Below is a link containing all the relevant XAML from the dependent components. This includes:

• A container user control that hosts a XamTileView bound to a collection of dashboard content items
• A further container control that sits in each TilePane and hosts the visualisation (chart/grid etc.)
• An example visualisation control (showing details of KPIs)