Now that you can pass in separate Navigation parameters, it makes it a little difficult to use the Navigation Journal, as this does not include them.
Before I would do this:
var params = new UriQuery();
params.Add("SomeId", _someId.ToString());
regionmanager.RequestNavigate("SomeRegion", "SomeView" + params);
But now it would ideally be:
var params = new UriQuery();
params.Add("SomeId", _someId); //As an int
regionmanager.RequestNavigate("SomeRegion", "SomeView", params);
But this now means that the NavigationJournal is not aware of the parameters. And so on IsNavigationTarget method it cannot compare if it is the correct viewmodel and so tries to open up a new one. As in some views they are editing records, so it always brings the same one back if they are editing that one.
Before I would do this:
var params = new UriQuery();
params.Add("SomeId", _someId.ToString());
regionmanager.RequestNavigate("SomeRegion", "SomeView" + params);
But now it would ideally be:
var params = new UriQuery();
params.Add("SomeId", _someId); //As an int
regionmanager.RequestNavigate("SomeRegion", "SomeView", params);
But this now means that the NavigationJournal is not aware of the parameters. And so on IsNavigationTarget method it cannot compare if it is the correct viewmodel and so tries to open up a new one. As in some views they are editing records, so it always brings the same one back if they are editing that one.