Hodentek Mobile

Windows evolved from just windows to include 'phones'. When Windows 8.1 was introduced Windows Runtime(WinRT) which was evolution of Windows app model came up with the Universal Windows 8 apps for both Windows and Windows Phone. Windows and Windows Phone shared a ccommon piece of code. Universal Windows Platform was introduced beginning Windows 10. The target was no more the Windows OS or Windows Phone OS but a common platform with a unified core. This core runs on all devices in the Windows family. Devices running this core can target can not only call WinRT APIs that are common to all devices but also Win32 and .NET APIs that are specific to device family. This means all you need to develop is a single app package that can be installed on a wide variety of devices shown here. UWP_00.PNG On any device, you have therefore, the guaranteed core and you add APIs on top of it specific to the device. You will conditionally access the device specific featur...

Verily, I say unto you, out of chaos a star is born Microsoft created a number of OSs to address diverse devices it had to contend with. This has resulted in a number of OSs with their own toolset and deployment strategies: such as, Windows CE Windows Embedded Windows Mobile Windows Desktop Windows Server Xbox OS Windows 10 has boldly replaced all of them with UAP , the Windows 10 Universal Application Platform. With UAP you need only to build once and it would run on any Windows 10 device. However devices are not built the same way across device types. In addition to Windows 10 UAP you would also need to target your application to specific device family be it desktop, be it mobile, or something different. So one way to address this is by adding reference to extension SDK for the device family. Here is how you would add a reference to Windows Mobile extension SDK from an article by Nick Randolph   In a real world diverse devices exist with their...