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

New Post: Register module from "Executable" instead of Library

$
0
0
Hi,

Based on my understanding, adding an .exe assembly file to the configuration file is the same as with other modules you added, but instead of ".dll" extension, you will use ".exe" extension in the assemblyFile field, which refers to the ".exe" file of your MainProject. Therefore, your configuration file should look like this:
<?xmlversion="1.0"encoding="utf-8"?><configuration><configSections><sectionname="modules"type="Microsoft.Practices.Prism.Modularity.ModulesConfigurationSection, Microsoft.Practices.Prism"/></configSections><modules><moduleassemblyFile="ModuleALibrary.dll"moduleType="ModuleALibrary.ModuleA, ModuleALibrary"moduleName="ModuleA"/><!-- Main module depends upon the modules above --><moduleassemblyFile="ModuleBLibrary.dll"moduleType="ModuleBLibrary.ModuleB, ModuleBLibrary"moduleName="ModuleB"><dependencies><dependencymoduleName="ModuleA"/></dependencies></module><!-- Main module configuration --><moduleassemblyFile="MainProject.exe"moduleType="MainProject.MainModule, MainProject"moduleName="MainModule"><dependencies><dependencymoduleName="ModuleB"/></dependencies></module></modules></configuration>
Take into account that assemblyFile and moduleType could differ slightly depending on your MainProject assembly name and default namespace properties.

Regards,

Federico Martinez
http://blogs.southworks.net/fmartinez

Viewing all articles
Browse latest Browse all 1878

Trending Articles



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