Replies: 1 comment 2 replies
-
If you have a dynamic module then don't register it in code. It needs to be loaded dynamically. If your dynamic module depends on other modules, then those modules need to be available to your application as well as all of their dependencies. You can read about how to load modules here: https://prismlibrary.com/docs/modules.html#registering-and-discovering-modules |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, thank you for the cool framework. I am setting up a new WPF .Net framework project and currently plan to running it with Prism.Unity. Everything is working great but I stucked on issue to override registered module by dynamic module.
My plan is to develop a standard logic application module by module, and if customization required, then can build individual module and run as a dynamic module.
Currently I able to load dynamic module, but I found the registered module always come before the dynamic module.
It will only working if I remove the reference of Module1Module and load dynamic module.
Even I don't perform moduleCatalog.AddModule<>(); and let module link in the reference, the dynamic module will not working as well.
Hope to get some advice on this. Thank you in advance and appriciate
Below is my sample project:
PrismDemo.zip
Beta Was this translation helpful? Give feedback.
All reactions