Prism Integration with docking

Hi,

Sample for PrismIntegration consists of ImplicitTemplate file that shows the DataTemplate for the views that needs to be docked .

Code for ImplicitTemplate dictionary.

-------------------------------------------------------------------

<ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"xmlns:sampleViewModels="clr-namespace:ActiproSoftware.Windows.PrismIntegration.ViewModels"xmlns:sampleViews="clr-namespace:ActiproSoftware.Windows.PrismIntegration.Views"><!-- Documents -->

<DataTemplate DataType="{x:Type DataTemplate DataType="{x:Type sampleViewModels:SolutionExplorerToolItemViewModel}">

<sampleViews:SolutionExplorerToolItemView />

</DataTemplate>

</ResourceDictionary>

--------------------------------------------------------------------

Question 1: ViewModel class(SolutionExplorerToolItemViewModel) that is used above is the data binding class for the view(SolutionExplorerToolItemView) or the class for handle the docking concept for the view(SolutionExplorerToolItemView) ? 

Question2:Suppose sample application is  registering the view with in the region and that view can be docked or float with  in the application which is implememnted with the help of PrismIntegartion with docking.Then how to handle the data binding of the contols used inside the view ?

Hi Keshav,

1. I'm sorry, but I don't understand the question. The view models are the items that the DockSite is bound to (using DocumentItemsSource and/or ToolItemsSource) and the view is the actual WPF control that is used to present it. This is typically done via DataTemplates that are applied implicitly, like we show above. The view is presented by an instance of our DocumentWindow or ToolWindow (as it's content) so it's really independent of our product.

2. The SolutionExplorerToolItemViewModel will end up being the data context (i.e. DataContext) of the associated view, which in this case is the SolutionExplorerToolItemView control. So inside that control you can do things like "{Binding MyProperty}", where MyProperty is a property on SolutionExplorerToolItemViewModel. The document views and view models show how this is accomplished, but the same concept applies to tool windows.