[Win10 UAP] Unable to inject own INavigationService about prism

[brianlagunas]

As you eluded to, Prism for WinRT is not support in this version, and is likely to be deprecated in favor of new guidance for the Windows UAP platform. When we start looking at Prism for UAP, we will be looking at improvements to the navigation service altogether.

[briannoyes]

Bart could you confirm this is solved now?

[briannoyes]

@bartlannoeye Ping - this one still an issue?

[bartlannoeye]

I've checked the code for PrismApplication and the method mentioned above is still private, but some deeper research opens up an alternative solution.

The NavigationService property is editable, so you're able to set it to your own implementation after the base class completed InitializeFrameAsync. The only thing missing if you would set the NavigationService property is restoring state (PrismApplication line 222) which could be done by the implementer of the new service. If someone would want to set his own NavigationService, it should be done by overloading OnLaunched and setting the property after calling base.OnLaunched.

Knowing how rare it is for someone to have to implement his own NavigationService, I think above scenario is flexible enough. Making the CreateNavigationService overridable (or provide another hook) would maybe make it too complex, making regular Prism users wonder why this is possible to override.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.