Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

UWP can't set target to Windows 10240

I have some trouble getting started with the Universal Windows Platform. Herefor I've installed the Visual Studio 2015 Community version, and I can succesfully create an App and run it on my Raspberry Pi with Windows 10 IoT Core. But my problem is that I cannot get the designer visible in the XAML files. Now have I found an answer to this in the following post:

Universal Windows App Visual Studio 2015 Community no designer, no controls in toolbox, no properties

Here I read that I have to set my target version to Windows 10240. This could be correct, because my current Windows 10 version is 10240, but for some reason I cannot set it to 10240. I can set the minimum version to 10240, but on the target version is only 10586 visible. Does anyone know what the reason of this is?

Please find the below screenshot for more information.

enter image description here

I've also tried to get my Windows 10 to update to 10586 (November Update), but this update fails, I guess maybe because my Users directory is on the D: Drive. Click here for my Windows Version Screen

like image 762
Roel Balink Avatar asked Mar 23 '16 06:03

Roel Balink


People also ask

Does UWP work on Windows 11?

Compatibility. UWP is a part of Windows 10, Windows 10 Mobile and Windows 11. UWP apps do not run on earlier Windows versions. Apps that are capable of implementing this platform are natively developed using Visual Studio 2015, Visual Studio 2017, Visual Studio 2019 or Visual Studio 2022.

Is UWP deprecated?

Microsoft continues to baby-step around the obvious, but it has officially deprecated the Universal Windows Platform (UWP) as it pushes the desktop-focused Windows App SDK (formerly called Project Reunion) and WinUI 3 as the future of Windows application development.

Does UWP support .NET 5?

NET 5/6 Will Not Be Coming to UWP Project Types,' Developers Sound Off -- Visual Studio Magazine.


1 Answers

For this and all related problems, your best bet is to go to the dev center and check there.

In this case, it looks like you are missing the SDK that targets the build 10240 of Windows 10, which can be found on this link.

enter image description here

like image 92
Nahuel Ianni Avatar answered Oct 24 '22 20:10

Nahuel Ianni