Navigating in PCL using Prism

Question

I'm building a UWP application with PCL using prism.

PCL contains the ViewModels

UWP contains the Views

My problem is I cannot use INavigationService in the PCL so I can't really navigate to other pages.

Here is my code:

MainPage.xaml (in UWP project):

<Grid Background="{ThemeResource ApplicationPageBackgroundThemeBrush}">

        <SplitView x:Name="RootSplitView"
                   DisplayMode="Overlay"
                   IsTabStop="False">
            <SplitView.Pane>
                <StackPanel Margin="0,50,0,0">
                    <Button Content="Second" Command="{x:Bind ViewModel.SecondPageCommand}"  />
                    <Button Content="Third" />
                </StackPanel>
            </SplitView.Pane>

            <!-- OnNavigatingToPage we synchronize the selected item in the nav menu with the current page.
                 OnNavigatedToPage we move keyboard focus to the first item on the page after it's loaded and update the Back button. -->
            <Frame x:Name="FrameContent" />
        </SplitView>

        <ToggleButton x:Name="TogglePaneButton"
                      TabIndex="1"                      
                      IsChecked="{Binding IsPaneOpen, ElementName=RootSplitView, Mode=TwoWay}"
                      ToolTipService.ToolTip="Menu"
                      Style="{StaticResource SplitViewTogglePaneButtonStyle}"
                      />
    </Grid>

ViewModel (in the PCL):

 public class NavigationRootViewModel : BindableBase
    {
        public ICommand SecondPageCommand { get; set; }
        public NavigationRootViewModel()
        {
            SecondPageCommand = DelegateCommand.FromAsyncHandler(ExecuteMethod);
        }

        private Task ExecuteMethod()
        {
            return Task.FromResult(0);
        }
    }

My wish was to inject INavigationService in the constructor but it's not part of the Prism.Core dll.

So what is the correct way to do it? Is it even possible to navigate in PCL using Prism ? in MvvmCross it is...

score 0 · Answer 1 · answered Sep 03 '16 at 13:22

0

I used prism navigation in our project as follows.

var regionManager = container.Resolve<IRegionManager>();
if (screenName == SpEnums.ViewName.LuminationView.ToString())
{
     regionManager.RequestNavigate(Enums.Regions.MainRegion.ToString(),
     SpEnums.ViewName.LuminationView.ToString());
}
else if()...

screen name is a property in navigation viewmodel.

Hope this helps.

answered Sep 03 '16 at 13:22

FreeMan

1,417
14
20

i know region manager from WPF apps. it's not part of prism core therefore not usable in PCL – kaycee Sep 03 '16 at 13:40

Martin Zikmund · Accepted Answer · 2016-09-03T20:18:24.123

Navigation is not built in a cross-platform manner in Prism, so it will not work without your own code.

To solve this, create an IAppNavigationService interface in the PCL:

public interface IAppNavigationService
{
    bool Navigate(string pageToken, object parameter);
    void GoBack();
    bool CanGoBack();
}

Implement it in the Windows project, basically just as a wrapper around the INavigationService, which you can also inject:

public class AppNavigationService : IAppNavigationService
{
   private readonly INavigationService _nav;

   public AppNavigationService( INavigationService navigationService )
   {
      _nav = navigationService;
   } 

   public bool Navigate(string pageToken, object parameter) => 
      _nav.Navigate( pageToken, parameter );

   public void GoBack()
   {
      _nav.GoBack();
   }

   public bool CanGoBack() => _nav.CanGoBack();
}

Do not forget to register the AppNavigationService class in the dependency injection container in App.xaml.cs.

Now in your PCL ViewModels you can just inject and use the IAppNavigationService for navigation.

yup that's a good answer. decorator pattern will do the work. just weird how come prism doesn't support navigation in PCL out of the box. Thanks — kaycee, Sep 04 '16 at 09:20
It is probably because there are differences between the navigation paradigms used on different platforms, so having this enables you to factor out exactly what you need. MvvmCross on the other hand has a great solution, which is also extensible. — Martin Zikmund, Sep 04 '16 at 10:17

Navigating in PCL using Prism

MainPage.xaml (in UWP project):

ViewModel (in the PCL):

2 Answers2