Windows App SDK (formerly known as Project Reunion ) is a software development kit (SDK) from Microsoft that provides a unified set of APIs and components that can be used to develop desktop applications for both Windows 11 and Windows 10 version 1809 and later. The purpose of this project is to offer a decoupled implementation of capabilities which were previously tightly-coupled to the UWP app model. Windows App SDK allows native Win32 ( USER32 / GDI32 ) or .NET ( WPF / WinForms ) developers alike a path forward to enhance their apps with modern features.
17-618: It follows that Windows App SDK is not intended to replace the Windows SDK . By exposing a common application programming interface (API) primarily using the Windows Runtime (WinRT) through generated WinMD metadata, the tradeoffs which once characterized either app model are largely eliminated. NuGet packages for version 1.4 were released in August 2023 after approximately four months of development. While Microsoft has developed
34-401: A number of new features, some of the features listed below are abstractions of functionality provided by existing APIs. Most of the investment into the decoupled UI stack has gone towards bug fixes, improvements to the debugging experience, and simplifying the window management capabilities made possible by switching from CoreWindow. An API abstracting USER32/GDI32 primitives known as AppWindow
51-1038: A particular reason. For example, the Windows Server 2003 Platform SDK released in February 2003 was the last SDK to provide full support of Visual Studio 6.0. Some older PSDK versions can still be downloaded from the Microsoft Download center; others can be ordered on CD/DVD. Last Platform SDK to officially install on Windows 95 Also known as Microsoft Platform SDK for Windows 2000 RC2. Includes Alpha to AXP64 cross toolset. Last Platform SDK to fully support Visual C++ 5.0 Also known as Microsoft Platform SDK for Whistler Beta 1. Includes preliminary tools for Itanium. Last Platform SDK to officially develop for Windows 95 . (Does not officially install on Windows 95 ) Last Platform SDK to unofficially develop for Windows 95 . (Does not officially install on Windows 95 ) Includes ARM64 support for
68-464: A result, the "IA-32" term may be used as a metonym to refer to all x86 versions that support 32-bit computing. Within various programming language directives, IA-32 is still sometimes referred to as the "i386" architecture. In some other contexts, certain iterations of the IA-32 ISA are sometimes labelled i486 , i586 and i686 , referring to the instruction supersets offered by the 80486 ,
85-508: Is a decoupled version of the resource management system from UWP. With the stable releases delivered after its initial launch, Windows App SDK now supports several app lifecycle features which previously required a considerable amount of effort for developers to implement in Win32 applications. These features include power management notifications, rich activation, multiple instances, and programmatic app restart. Support for push notifications
102-402: Is dedicated to developing applications for .NET Framework 1.1 and .NET Framework 2.0 . Windows SDK is the successor of the two and supports developing applications for Windows XP and later, as well as .NET Framework 3.0 and later. Platform SDK is the successor of the original Microsoft Windows SDK for Windows 3.1x and Microsoft Win32 SDK for Windows 9x . It was released in 1999 and
119-493: Is the oldest SDK. Platform SDK contains compilers , tools, documentations, header files, libraries and samples needed for software development on IA-32 , x64 and IA-64 CPU architectures . .NET Framework SDK however, came to being with .NET Framework . Starting with Windows Vista , the Platform SDK, .NET Framework SDK, Tablet PC SDK and Windows Media SDK are replaced by a new unified kit called Windows SDK . However,
136-584: The P5 and the P6 microarchitectures respectively. These updates offered numerous additions alongside the base IA-32 set including floating-point capabilities and the MMX extensions . Intel was historically the largest manufacturer of IA-32 processors, with the second biggest supplier having been AMD . During the 1990s, VIA , Transmeta and other chip manufacturers also produced IA-32 compatible processors (e.g. WinChip ). In
153-402: The .NET Framework 1.1 SDK is not included since the .NET Framework 1.1 does not ship with Windows Vista. (Windows Media Center SDK for Windows Vista ships separately.) DirectX SDK was merged into Windows SDK with the release of Windows 8. Windows SDK allows the user to specify the components to be installed and where to install them. It integrates with Visual Studio , so that multiple copies of
170-480: The Visual Studio 17.4 release The Windows SDK documentation includes manuals documenting: IA-32 IA-32 (short for " Intel Architecture, 32-bit ", commonly called i386 ) is the 32-bit version of the x86 instruction set architecture , designed by Intel and first implemented in the 80386 microprocessor in 1985. IA-32 is the first incarnation of x86 that supports 32-bit computing; as
187-627: The Windows App SDK and considered to be the recommended application packaging format, a design goal was to allow for unpackaged apps. These apps can be deployed as self-contained or framework-dependent. Support for dynamic loading of app dependencies is included for both packaged and unpackaged apps. DWriteCore is being developed as a decoupled and device-independent solution for high-quality text rendering. Win2D has also been made available to WinUI 3 apps. MRT Core allows for management of app resources for purposes such as localization. It
SECTION 10
#1732790163979204-789: The Windows Widgets system in Windows 11 has been included as part of the stable release channel. Developers can design custom widgets for their app using adaptive cards and surface them on the widgets board. Microsoft Windows SDK Microsoft Windows SDK , and its predecessors Platform SDK , and .NET Framework SDK , are software development kits (SDKs) from Microsoft that contain documentation , header files , libraries , samples and tools required to develop applications for Microsoft Windows and .NET Framework . Platform SDK specializes in developing applications for Windows 2000 , XP and Windows Server 2003 . .NET Framework SDK
221-495: The components that both have are not installed; however, there are compatibility caveats if either of the two is not from the same era. Information shown can be filtered by content, such as showing only new Windows Vista content, only .NET Framework content, or showing content for a specific language or technology. Windows SDKs are available for free; they were once available on Microsoft Download Center but were moved to MSDN in 2012. A developer might want to use an older SDK for
238-593: The contemporary prevalence of x86-64, as of today, IA-32 protected mode versions of many modern operating systems are still maintained, e.g. Microsoft Windows (until Windows 10 ), Windows Server (until Windows Server 2008 ) and the Debian Linux distribution. In spite of IA-32's name (and causing some potential confusion), the 64-bit evolution of x86 that originated out of AMD would not be known as "IA-64", that name instead belonging to Intel's Itanium architecture . The primary defining characteristic of IA-32
255-466: The modern era, Intel still produced IA-32 processors under the Intel Quark microcontroller platform until 2019; however, since the 2000s, the majority of manufacturers (Intel included) moved almost exclusively to implementing CPUs based on the 64-bit variant of x86, x86-64 . x86-64, by specification, offers legacy operating modes that operate on the IA-32 ISA for backwards compatibility. Even given
272-468: Was initially implemented as a limited-access, preview feature. However, the APIs for it have since been stabilized and push notifications can be delivered to app users. Official documentation states that access to the feature can be revoked by Microsoft at their discretion. Additionally, apps can now easily display local app notifications without the need to create an XML payload. Third-party integration with
289-463: Was introduced to expose a unified set of windowing capabilities and enable support for custom window controls. A replacement for the UWP WebView control was announced early on. This is because it was based on an unsupported browser engine . A new Chromium -based control, named WebView2 , was developed and can be used from WinUI as well as other supported app types. While MSIX is included in
#978021