Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m building a little complex prism application. Customer requirements obliges me to utilize ModuleA features in ModuleB.
My question is whether it is breaking prism’s decoupling purpose when I reference ModuleA namespace in ModuleB and navigate to its views. If yes then how can I resolve this ?
You need to use the
IEventAggregatorand publish/subscribe to weak events (CompositePresentationEvent<TPayload>) through it.Here is a sample.
Here is the relevant msdn link.