Below is a skeleton of how a view definition looks like in a management pack.
<View ID="[UniqueViewID]" Target="[TargetClass]" Enabled="true" TypeID="Console!GridViewType" Accessibility="Public">
<Category>NotUsed</Category>
<Data>
<Adapters>
<Adapter>[Data Adapter]</Adapter>
<Adapter>[List Support Adapter]</Adapter>
</Adapters>
<ItemsSource>[List Support Class]</ItemsSource>
<Criteria>[Criteria]</Criteria>
</Data>
<Presentation>
<Columns>[Columns] </Columns>
<ViewStrings>[View Strings]</ViewStrings>
</Presentation>
</View>
Here is a detailed explation of what the configuration means:
ID is the unique name for the view
Target is the class that you want to target the view to
Enabled is a bool stating whether the view is enabled
Accessibility is whether this view can be referenced from other management packs
TypeID is the view type. We currently have 2 view types out of the box
1. GridViewType is defined in the console management pack. The configuration is <any> which enables to extend the xml configuration not specified by the schema. This post talks about grid view configuration
<ViewType ID="GridViewType" Accessibility="Public">
<Configuration>
<xsd:any minOccurs="0" maxOccurs="unbounded" processContents="skip" />
</Configuration>
<ViewImplementation>
<Assembly>WpfViewsAssembly</Assembly>
<Type>Microsoft.EnterpriseManagement.UI.WpfViews.GridView</Type>
</ViewImplementation>
</ViewType>
2. OverviewView Type. This is defined in the administration management pack. The configuration again is <any> which
enables to extend the xml configuration not specified by the schema. The view configuration for this will be discussed later.
<ViewType ID="OverviewType" Accessibility="Public">
<Configuration>
<xsd:any minOccurs="0" maxOccurs="unbounded" processContents="skip" />
</Configuration>
<ViewImplementation>
<Assembly>Console!WpfViewsAssembly</Assembly>
<Type>Microsoft.EnterpriseManagement.UI.WpfViews.Overview</Type>
</ViewImplementation>
</ViewType>
Data This section defines how the view gets it data. There are 3 areas within the Data that are needed namely Adapters, ItemsSource and Criteria (if needed)
1. Adapters: There are two adapters needed here, one for the purpose of where is the data fetched from and the other for the List View presentation
