StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19547777
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-10-23T16:55:08.143
FavoriteCount
0
LastActivityDate
2013-10-23T16:55:08.143
LastEditDate
LastEditorUserId
0
OwnerUserId
516708
ParentId
19526287
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I believe the PRISM view philosophy is to load all the views and switch them in and out like a stack of cards. In your case, I can see you are using an attached behavior to load all of your views for each region. I suspect that all of your views are being loaded and added to the appropriate region, but that the last view is over the others (having been added last to the region). In WPF, the last control in the view hierarchy is higher in the zorder (because it is the last to be painted). Each of the previous controls is likely underneath. Instead of your current approach, I suggest you create a service class called NavigationService, that will handle loading a view set from a module on demand, and unloading any previous view set. You can design it to be a state manager, and it can coordinate different view arrangements with PRISM, even if you only want certain views loaded (say a sub-set of a module's views), instead of loading all of the views all the time. In your Bootloader, register each module with the NavigationService, and perhaps have each module include a strategy class for each view combination you need, supplying appropriate behavior. This way you keep the coordination logic close to the views it uses. In your Shell, call the NavigationService (which will be injected into each of your view models to facilitate changing screens) to set the initial view. Remember, this is just an idea to accomplish what you need, but I would get away from the basic PRISM functionality in WPF. It is limiting, imho, and unnecessary in complexity. You can still use PRISM's regions without using its navigation facility. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWPF MEF + Prism initial Region loading
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USBahri Gungor
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COThanks for the response, it's a good comment and I'll look into something of this kind to replace the Prism behaviour as I don't like having to declare identical duplicated navigation controller helper code in each module
 singulars
 PostPostId
 PO
 UserUserId
 USNZJames

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.