Quantcast
Channel: patterns & practices: Prism
Viewing all articles
Browse latest Browse all 1878

New Post: Problem with PRISM migration and Framework version

$
0
0
We have migrated to prism 4 from CAL

However after the migration, the views are not injected to regions when we run the application on a machine with .Net 4.0.
The same code however works well on a machine with .Net 4.5 installed. Could this be possibly due to PRISM or any other component we may be using.

This is how our module catalog looks like
<module assemblyFile="MyApp.Modules.MyApp.dll" moduleType="SomeNamespace.CustomerSoftware.SRP.Modules.MyApp.SE_WPF_ModuleSchematic" moduleName="Schematic"/>
<module assemblyFile="MyApp.Modules.MyApp.dll" moduleType="SomeNamespace.CustomerSoftware.SRP.Modules.MyApp.SE_WPF_ModuleFBGrid" moduleName="DataGrid"/>
<module assemblyFile="MyApp.Modules.MyApp.dll" moduleType="SomeNamespace.CustomerSoftware.SRP.Modules.MyApp.SE_WPF_ModuleNetwork" moduleName="Network">
  <dependencies>
    <dependency moduleName="Schematic"/>
    <dependency moduleName="DataTree"/>
    <dependency moduleName="DataGrid"/>
  </dependencies>
</module>
<module assemblyFile="MyApp.Modules.MyApp.dll" moduleType="SomeNamespace.CustomerSoftware.SRP.Modules.MyApp.SE_WPF_ModuleFBtree" moduleName="DataTree"/>
<module assemblyFile="MyApp.Modules.MyApp.dll" moduleType="SomeNamespace.CustomerSoftware.SRP.Modules.MyApp.SE_WPF_ModuleSolution" moduleName="DataSolution"/>
<module assemblyFile="MyApp.Modules.MyApp.dll" moduleType="SomeNamespace.CustomerSoftware.SRP.Modules.MyApp.SE_WPF_ModuleProtectionCurve" moduleName="Plot"/>
Under module Network view constructor the regions are associated to the control
        RegionManager.SetRegionName(this.SchematicContent, RegionNames.SchematicRegion);
        RegionManager.SetRegionManager(this.SchematicContent, this.regionManager);

        RegionManager.SetRegionName(this.TreeContent, RegionNames.TreeRegion);
        RegionManager.SetRegionManager(this.TreeContent, this.regionManager);

        RegionManager.SetRegionName(this.GridContent, RegionNames.GridRegion);
        RegionManager.SetRegionManager(this.GridContent, this.regionManager);
The constructor for the presenter of this module then assigns the views to these regions
        this.schematicRegion = this.regionManager.Regions[RegionNames.SchematicRegion];
        this.schematicView = AddCompositeView(typeof(ISE_WPF_ModuleSchematicView), typeof(ISE_WPF_ModuleSchematicPresenter), schematicRegion);
        this.schematicRegion.Activate(schematicView);

        this.propertiesRegion = this.regionManager.Regions[RegionNames.TreeRegion];
        this.treeView = AddCompositeView(typeof(ISE_WPF_ModuleFBtreeView), typeof(ISE_WPF_ModuleFBtreePresenter), propertiesRegion);
        this.solutionView = AddCompositeView(typeof(ISE_WPF_ModuleSolutionView), typeof(ISE_WPF_ModuleSolutionPresenter), propertiesRegion);
        this.PlotView = AddCompositeView(typeof(ISE_WPF_ModulePlotView), typeof(ISE_WPF_ModulePlotPresenter), propertiesRegion);
        this.propertiesRegion.Activate(this.treeView);


        this.gridRegion = this.regionManager.Regions[RegionNames.GridRegion];
        this.gridView = AddCompositeView(typeof(ISE_WPF_ModuleFBGridView), typeof(ISE_WPF_ModuleFBGridPresenter), gridRegion);
        this.gridRegion.Activate(this.gridView);


Viewing all articles
Browse latest Browse all 1878

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>