https://www.youtube.com/watch?v=cBgMPW-Bcx8

Using the tutorial shown by the youtube. I use Visual Studio 2015 upgrade 3 App Map Extension to create the visual studio project. 

Without using the NavigateAbsoluteCommand - Only the standard NavigateCommand, all Navigation Works.

So, NavigateAbsoluteCommand  code created by the Visual Studio 2015 App Map extension causes error.

I was confused because you can't create a UWP app with the AppMap.  However, I manually added an UWP app and see what you mean.  It seems the URI format is evaluated differently on UWP.  Will be an easy fix. For now, just manually change the command to use the NavigateCommand instead of the NavigateAbsoluteCommand.  As long at the target URI has a "/" in front of it, it will be seen as an absolute navigation.

Thanks,

Dear Brian, do you have time to figure out the "fix" and could you share with me the "fix", so I could continue to develop and promote App Map for UWP? Thnx

As I mentioned in my previous post, you can manually change your Command to use the NavigateCommand

Change:

Command="{Binding Path=NavigateAbsoluteCommand}" CommandParameter="/PageName"

To:

Command="{Binding Path=NavigateCommand}" CommandParameter="/PageName"

Another option would be to just change the NavigateAbsoluteCommandExecute method in the AppMapViewModelBase class

Change:

await this.NavigationService.NavigateAsync(new Uri(uri, UriKind.Absolute), null, false);

To:

await this.NavigationService.NavigateAsync(uri, null, false);

Got it. Thanks