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.

Got it. Thanks

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);

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

Thanks for prompt reply. It is great that there is NOW a plan to include UWP.

In my impression, most of us who are porting XF controls for UWP have been doing customRendering using ideas from https://github.com/telerik/UI-For-UWP

I believe having well integrated XF controls and App Map adapted for UWP will give infragistics some advantages. There are still significant vacum in use case, examples and tools to simplify Xamarin Forms for UWP development. Your organization commitment to bring XF controls and App Map to UWP will be welcome to UWP XF community.

The reason UWP is not include in the AppMap is because our XF controls currently do not support UWP.  It's not a limitation in the AppMap directly, and can easily be added.  We realize that UWP is starting to gain more interest and we are planning on adding UWP support by Oct/Nov timeframe.