Cannot build project (DUE TO LACK OF DOCUMENTATION OF BUILD STEPS)

[manups4e]

Mainly it "cannot create NavigationViewItem in XAML"

[deankevorkian]

Hey, are you on the latest visual studio version? Also ensuring - do you have UWP and .NET Core 3.0 both installed? I don't find anything online to suggest issue rather than people with issues in Visual Studio. Also tried a clean clone of the code and it seems building both in my desktop and laptop. I feel like it's a missing component in the vs installation but don't know for sure

…

On Sun, Jan 3, 2021, 8:14 PM Leonardo Emanuele ***@***.***> wrote: Mainly it "cannot create NavigationViewItem in XAML" [image: image] <https://user-images.githubusercontent.com/4005518/103485593-bb536e00-4df7-11eb-8ee1-6d7318fafa04.png> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#27>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADQ3UPSTKJKRJ7KXGAIU55LSYCXXNANCNFSM4VSCDDQQ> .

[manups4e]

i do have everthing updated yet i don't seem to be able to build it.. i downloaded the project directly from master branch and opened its sln file

[manups4e]

i tried to re-download nugets packages for the project but still it gives me this..

[deankevorkian]

So basically the issue is solved but the reason for it being opened is the lack of precise documentation -
The project would not compile for @manups4e for several reasons -

1. The solution configuration architecture should've been x64 (I'll admit ARM and x86 are, as of now, not supported - as most SDKs we use for physical control of devices only support x64, or to the very least - we have only supported x64 for them). This might change in the future as we consolidate direction for going cross platform.
2. The startup project should've been the WAP (RgbMasterWap project) - this is due to limitations regarding WPF & UWP (via Xaml Islands) that require us to run the WAP project for certain features to work. Might change in .NET 6
3. the WAP project had to be signed (and since we won't disclose our password for the private key, as it will use us for publishing on the Microsoft Store, you have to create a certificate of your own)

I'm gonna allow myself to change the issue title to include "MISSING DOCUMENTATION" and keep it open - but it is resolved.