Hi James,
The next drop of Prism has this issue addressed, as navigation parameters are saved in the Navigation Journal. However, as a very easy workaround for now, you could use the old approach of passing query string parameters, since you just needs an int to be passed, in the following way.
var params = new NavigationParameters();
params.Add("SomeId", _someId); //As an int or string
regionmanager.RequestNavigate("SomeRegion", "SomeView" + params.ToString());
This is the old way of doing it and it is still supported in Prism, but now the UriQuery class is renamed to NavigationParameters, maintaining the old functionality and adding support for object parameters.
Hope this helps,
Diego Poza
The next drop of Prism has this issue addressed, as navigation parameters are saved in the Navigation Journal. However, as a very easy workaround for now, you could use the old approach of passing query string parameters, since you just needs an int to be passed, in the following way.
var params = new NavigationParameters();
params.Add("SomeId", _someId); //As an int or string
regionmanager.RequestNavigate("SomeRegion", "SomeView" + params.ToString());
This is the old way of doing it and it is still supported in Prism, but now the UriQuery class is renamed to NavigationParameters, maintaining the old functionality and adding support for object parameters.
Hope this helps,
Diego Poza