Like you said there are a number of things you can do: You could expose a property on MyViewModel and set it within MainWindowView You could use the EventAgregator publish an event from the MainWindowView and subscribe to that event from MyViewModel Using MEF you could inject a shared resource between the two ViewModels, set it in MainWindowViewModel and be able to access it from MyViewModel.
Like you said there are a number of things you can do: You could expose a property on MyViewModel and set it within MainWindowView. You could use the EventAgregator, publish an event from the MainWindowView and subscribe to that event from MyViewModel. Using MEF you could inject a shared resource between the two ViewModels, set it in MainWindowViewModel, and be able to access it from MyViewModel.
Thanks for the ideas. Regarding #3, we don't use MEF. Is there another way we could do that?
Say with a normal DI toolkit. – basilard99 Aug 11 at 2:04 Sure, I sometimes create a SharedData class implementing ISharedData. It should be no problem to property or constructor inject a shared instance with the other DI tools.
– Derek Beattie Aug 11 at 2:49 caliburnmicro.codeplex. Com/discussions/262097 – Derek Beattie Aug 11 at 2:57.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.