Databases
StackOverflow2013
Postsdbo
POWPF MEF + Prism initial Region loading
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWPF MEF + Prism initial Region loading
    primarykey
    data
    text
    <p>I have written an MVVM app in WPF using MEF and Prism with three different regions. Code is across two modules, being discovered in the App.Config.</p> <p>I have all the navigation commands and structure working perfectly fine, but the one thing I am confused on is how to set the initial Views loaded into each region at app startup as there seems to be nowhere I can do this. Furthermore if I add something to the end of the MainViewModel constructor to explicitly navigate to screen set A, something else seems to be overriding it and loading a different set of views to start with.</p> <p>It also seems dependent on what order I load the modules in on the app.config which seems undesirable. If I load the Admin module last, it loads a set of screens from the admin module, if I load the search module last, it loads a set of views from the search module and in this case, it is not even finding a View for the main region.</p> <p>What is the method for specifying what Views are loaded into each region at app startup when using MEF and config discovery?</p> <pre><code>using System; using System.ComponentModel.Composition; using Microsoft.Practices.Prism.Regions; namespace CRM.GUI.WPF.Shared.Infrastructure.Behaviour { [Export(typeof(AutoPopulateExportedViewsBehavior))] [PartCreationPolicy(CreationPolicy.NonShared)] public class AutoPopulateExportedViewsBehavior : RegionBehavior, IPartImportsSatisfiedNotification { protected override void OnAttach() { AddRegisteredViews(); } public void OnImportsSatisfied() { AddRegisteredViews(); } private void AddRegisteredViews() { if (Region != null) { foreach (var viewEntry in RegisteredViews) { if (viewEntry.Metadata.RegionName == Region.Name) { var view = viewEntry.Value; if (!Region.Views.Contains(view)) { Region.Add(view); } } } } } [ImportMany(AllowRecomposition = true)] public Lazy&lt;object, IViewRegionRegistration&gt;[] RegisteredViews { get; set; } } } [AttributeUsage(AttributeTargets.Class, AllowMultiple = false)] [MetadataAttribute] public class ViewExportAttribute : ExportAttribute, IViewRegionRegistration { public ViewExportAttribute() : base(typeof(object)) { } public ViewExportAttribute(string viewName) : base(viewName, typeof(object)) { } public string RegionName { get; set; } } </code></pre> <p>Used</p> <pre><code>[ViewExport(RegionName = RegionNames.MainRegion)] public partial class ReportView </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USNZJames
    1. USNZJames
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWPF MEF + Prism initial Region loading
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHi! It's really hard to tell. Do you have a region behavior which imports the views? Can you post it?
      singulars
      1. POWPF MEF + Prism initial Region loading
      1. USMarc
    2. COUpdated to include code
      singulars
      1. POWPF MEF + Prism initial Region loading
      1. USNZJames
    3. COLooks good, if you set abreakpoint in the OnAttach() method: Is it hit, are what does `RegisteredViews` contain? Can you post the shell, too?
      singulars
      1. POWPF MEF + Prism initial Region loading
      1. USMarc
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload