Dec 10, 2010 at 5:29 PM
Edited Dec 10, 2010 at 5:41 PM
Thanks for your answers!
I have acctually looked at your Sample Application. Nice work! It's always great to see a complete app to get a feeling of how to structure your own app.
And thats kind of also where my question came from. I tend to think that you shouldn't put to much logic into your constructors. It's not the nicest place to get exceptions etc. in. And I usually want to avoid having a lot of calls to private methods
etc. in there.
But in the MVVM case it seems that you don't have to much of a choice. I tried to load my data in OnActive but the method won't get called in my app?
The OnActivate method gets called when I from my 2:nd screen press the Back button to get to my first screen. But when I start the application or when I use:
_navigationService.Navigate(new Uri("/SomePage.xaml", UriKind.Relative));
It is not called.
My ViewModel for SomePage.xaml inherits frm Screen and implements ILaunchChooser<PhotoResult>
Am I missing something here perhaps?
EDIT: Humm I might have missed the ScreenConductor thing. I'll try some tests with this and see if it helps! :)
Thanks again for taking time to answer my questions.