I have a Prism shell (CAL) with specific areas. Each region is responsible for its own navigation log, and some regions inherit from the parent.
The problem is that you cannot define Prism areas in the frame content template. What is the best approach to implement NavigationServices in Shell.xaml and enjoy using it with Prism.
The following code causes the region manager to cry about not finding the area. I understand why, but I would like some input to the best practice.
<Frame JournalOwnership="OwnsJournal" NavigationUIVisibility="Hidden">
<Frame.Content>
<DockPanel>
<ItemsControl Name="NavigationFrame" DockPanel.Dock="Top"
cal:RegionManager.RegionName="{x:Static p:TopLevelShellRegionNames.NavigationRegion}"/>
<Grid>
<ContentControl Name="ContentFrame"
cal:RegionManager.RegionName="{x:Static p:TopLevelShellRegionNames.ContentRegion}"/>
</Grid>
</DockPanel>
</Frame.Content>
</Frame>
Thank.
source
share