Navigate to a Page of another Class Library

Question

I need to create several versions of a core project. Few things can change between core project and its extensions, some functionalities and, above all, design (Fonts, colors, e

Answer 1

Luckily there is a workaround by Daniel Vaughan (http://danielvaughan.org/post/UWP-AccessViolationException-when-Navigating-to-a-Page-in-Another-Assembly.aspx):

• create a Dummy.xaml in the startup project

Answer 2

halllo's answer only works for me in Debug build. When I build/deploy in Release build, the problem is still there. Instead, I just remove the Navigation code and assign the content directly. So far my app works well (since I don't need Navigation, it's a single WebView app) but I do not know if there will be any problem.

// rootFrame.Navigate(typeof(MainPage), e.Arguments);
// Remove the above default line
// MainPage is a C# class that inherits a Page in my library
rootFrame.Content = new MainPage();