Пакет средств разработки программного обеспечения sdk для windows

From Wikipedia, the free encyclopedia

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.^[1] Platform SDK specializes in developing applications for Windows 2000, XP and Windows Server 2003. .NET Framework SDK 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.^[2]

Features[edit]

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 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, 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.^[3]

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 the components that both have are not installed; however, there are compatibility caveats if either of the two is not from the same era.^[4][5] 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 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.^[6]

Documentation[edit]

The Windows SDK documentation includes manuals documenting:

• Desktop app development with Windows API and managed code
• Metro-style app development using Windows Runtime and Universal Windows Platform
• Web app development using ASP.NET, HTML, CSS and JavaScript
• Language-related topics for C++, C#, Visual Basic.NET, F#, JavaScript, CSS and HTML, such as syntax and conventions (Windows PowerShell language is not covered.)

See also[edit]

• MSDN Library
• Windows Driver Kit
• Windows App SDK
• Windows 10 Version History

References[edit]

External links[edit]

• Windows SDK Blog
• Windows SDK Archive

Have you ever thought about the number one leverage of coding? Interestingly, this most precious edge is primarily invisible. Our regular usage hides this edge from us. Here, we will first discuss the concept of code leverage. Then we will answer many questions like an SDK, its purpose, API vs. SDK, the Windows software development kit, etc.

Moreover, we will see how modern tools like Delphi, C++ Builder, and RAD Studio make life easier. These tools handle many intricacies of setting up different SDKs. If you are into Windows development, you will find this information handier. But these concepts are also helpful on other platforms.

What is a code leverage?

Surely, each of us wants an easier and successful life, especially when it comes to our work. Leverage can be a boon when striving for success when there is a resource shortage and competition is vigorous. There can be many types of leverage, like leverage of labor, exposure, money, but coding leverage excites me the most.

Just imagine for a moment taking several years to code a solution which finds traction among an army of developers. And then someone emerges who provides all that functionality to other coders for free (or monetized in a way you can’t match) through some form of APIs or code reuse techniques. Compare it with writing as an author. You can not write a 1000-page novel by copying 990 pages written by someone else. Even if it is permissible, no one will be interested in it because it is not offering any additional benefit.

On the other hand, coding is often standing on the shoulders of giants in a form of legal plagiarism if you legally use the available free code of others to solve a problem or add functionality. Then, combined with your own uniqueness and work it emerges again as your product. This kind of code reuse is the number one leverage of software development. It’s not always the final solution which is the pivotal element but the means to get to that point, the bricks and mortar of the house, not the finished home.

One of the many ways we reuse code, the metaphorical bricks and mortar, is the concept of a software development kit (SDK). Just like using good quality bricks and well-mixed cement RAD Studio with Delphi and Windows SDK can be the foundations of your success when you’re looking for the best IDE tools for Windows 10 and beyond.

What is a software development kit (SDK)?

A software developer needs many tools to develop an application. An SDK is a collection of such tools. For example, an SDK may include a compiler, debugger, framework, and software libraries. It also often contains documentation and sample code to guide the proper usage of the SDK and manage expectations for its capabilities. Also, an SDK generally targets specific hardware capabilities and operating systems.

Many SDKs are available for very specific platforms. For example, developers might use the Java Development Kit (JDK) for JAVA development. People wanting to work with Apple devices use the iOS SDK for iOS development. For Android development, we need an Android SDK. We also use Windows SDK for Windows development. SDKs might have license limitations. These limits dictate how a developer can use them. Also, SDKs have different versions. These versions often have limited backward compatibility. Thus, to use new features of a platform, you may need a more recent SDK. Also, there’s no precise definition of an SDK and for some the exact elements might vary.

Why do we need an SDK?

Although it is possible to develop some software without using an SDK, it is neither easy nor economical. Using an SDK makes our job as a programmer much more effortless since it typically reduces the work to interface with the operating system or hardware supported by the SDK. It also often brings to the table benefits of large amounts of research and best practices commonly with the benefit of very specific information from a hardware or software vendor which might not be readily accessible elsewhere. Using the SDK can help ensure our application behaves according to user expectations.

Generally with a platform-specific SDK for developing applications to work with that platform it’s an easier path to a working application. Creating software without an SDK for some systems is challenging, if not impossible, especially for heavily vertical single-vendor hardware solutions such as an iPhone.

What is the difference between a library and an SDK?

A library in the context of software development is a collection of reusable code you can call in your application. Chunks of code in a library are usually closely related to one another. For example a math function library. You can use this library instead of writing your own math functions. An SDK contains many libraries, among other things.

What is the difference between an API and SDK?

Although often confused, an API and an SDK are two different things. They are overlapped and interrelated but quite different in other ways. The term API stands for an Application Programming Interface. An API allows communication between two applications or software systems. Thus an API is an interface that provides service to other software. Thus:

• An API is usually a subset of an SDK.
• An SDK contains not only many APIs but also includes several other tools.
• An SDK may have many APIs, but an API cannot incorporate SDK.
• An API lays out in code definitions of how something should happen and the parameters and methods available.
• The SDK typically enables and facilitates the APIs to be accessible and function (in a general sense).
• APIs operate on a request and response model from one app or subsystem to another.
• API allows communication between apps, and SDK allows building apps.
• Not all APIs have an SDK companion.

What is the difference between an SDK, and a framework?

Sometimes there is a clear boundary between an SDK and a Framework. Other times it is a gray area. Many times they are used interchangeably, like .NET Framework SDK. Though both complement each other, there are essential differences that mostly hold. For example:

• An SDK is needed for application developers only, and application users do not directly need it.
• A Framework becomes part of the application. It is there to make the job of software developer easier.
• An SDK typically targets a particular OS/CPU type. A Framework can be multiplatform. For example, FireMonkey is a cross-platform framework for developing native applications.
• A Framework is like a prebuilt template of a software solution or capability.
• We solve problems at a more abstract and general level in a Framework than we do in an SDK or even an API.
• A Framework can make code reuse possible or more manageable.
• Some Frameworks might have a runtime component that should be present on the application user’s machine.

We can compare an application with a house. For example, a library will be a chair in a bedroom. We can build a chair ourselves. But buying a chair is better. An SDK will be a furniture set with assembling instructions. Finally, a Framework will be the structure of the whole house. Thus all three are closely related but differ in scope.

What is the Windows software development kit?

The Windows Software Development Kit or Windows SDK is a set of software development tools for Microsoft Windows. Currently, it is the most popular option to develop Windows apps. Windows SDK helps developers to create software solutions for the Windows platform. Windows SDK contains tools like command-line Windows compilers, debugging and performance testing tools, libraries, documentation, APIs, and samples.

Is there a brief history of the Windows Software Development Kit?

There are a lot of different versions of things which get called Windows Software Development Kit and it can be quite hard to unwind all of them especially since they tend to carry quite similar sounding names and offer functionality which crosses the boundaries of one another. Let’s try to unravel some of them for you!

What is the Microsoft Foundation Class library (MFC)?

MFC was the first UI library released in 1992. MFC wrapped the Component Object Model (COM) and Win32 APIs. It was a great success and many developers still regularly use it. Despite this MFC is not suitable for modern applications because it is popularly considered outdated and does not support modern hardware features such as touch input and HD displays.

What is the Microsoft Platform SDK?

The Microsoft Platform SDK contains documentation, header files, libraries, samples, and tools required to develop applications for Microsoft Windows. Platform SDK specialized in supporting development of applications for Windows 2000, XP, and Windows Server 2003.

What is the Microsoft Dot Net SDK?

The Windows SDK also includes .NET SDK to produce .NET applications. .NET Framework implements a Common Language Infrastructure (CLI). With CLI, developers can use many languages to develop applications. It also provides an extensive Framework Class Library (FCL) to make the job easier. .NET applications run on a virtual machine called Common Language Runtime (CLR). CLR provides security, memory management, and exception handling services. CLR makes the job of a developer more accessible.

However, this approach has two drawbacks. Firstly, the size of a .NET application (plus runtime support) can be enormous when compared to a native application. Secondly, the performance and execution speed of a .NET application is frequently less optimal than a native application. Fortunately, the Delphi VCL and FireMonkey frameworks provide the best of both worlds. You can write in your applications in the easy to learn and super-fast-to-compile Delphi or the equally powerful C++ languages. The rapid optimizing compiler then produces native applications which harness the full power of the Windows APs and libraries. These features make RAD Studio with Delphi the best Windows apps studio.

What is the Windows Software Development Kit?

The Windows Software Development Kit is currently the most popular SDK version. It contains many Windows tools for developers. It supports Windows program development for Windows XP and up to Windows 10. That means it supports Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows 8, and Windows 10. The current stable version release date is May 12, 2020. It also supports DOT NET framework 3.0 and up.

What Is next for the Windows SDK?

Microsoft have announced the Windows App SDK which is the next Windows SDK. Previously its name was Project Reunion. It supports Windows 10 app development (Version 1809 and up) and Windows 11. Released in November 2021, it is a relatively new entrant. It is an evolving project. It will take some time to catch on. If you don’t need the latest features of Windows App SDK, you can probably stick with the Windows Software Development Kit for several years to come.

How does Delphi help you manage SDKs?

You will need different SDKs for deploying to various operating system platforms. Also, you will need different versions of an SDK for some app development projects. Unfortunately, it isn’t easy to manually install and manage support for them. Fortunately, Delphi Windows IDE has a specific tool called Delphi SDK Manager. With this tool, you can manage all of the needed platform SDKs in one place. For example, you can manage macOS, iOS, and Android SDKs.

Why is Delphi the best companion for the Windows SDK?

Delphi was always at the forefront of rapid application development for Windows. It was the one of the first Rapid Application Development (RAD) tools yet it continues to actively evolve and embrace new development techniques, Windows SDK improvements, new platforms and multi-device targets. RAD Studio with Delphi helps programmers to develop applications fast. It has a lovely windows VCL (Visual Component Library) framework which is the supreme Windows UI toolkit and a hallmark of productive development on Windows. Also, its FireMonkey framework is at the leading edge of cross-platform development allowing developers to create apps which work on Windows, macOS, iOS, Android and Linux all from one single codebase. Delphi’s features, performance, and productivity make it the best Windows software maker for anything Windows and beyond. With the current popularity of Windows 10 development (and Windows 11 too), Delphi can be your best companion for Windows apps development.

Start developing with the Windows Software Development Kit now

Delphi is the most straightforward native Windows development software. Since its inception in 1995, every new version supported all new features and enhancements in the Windows platform on time. Now is your turn to use Delphi to develop Windows software. So to jumpstart your Windows software development journey by using the latest Windows SDK, download the best Windows development IDE now.

We are excited to announce that Windows App SDK 1.2 is now available! With WinAppSDK 1.2 you can now create widgets for the Windows 11 widget board, use the most modern WinUI controls – including media playback & InfoBadge, and support HDR graphics through the DisplayInformation APIs among other additional features. We have also made several updates to improve platform reliability, stability, and performance to help you create robust, powerful, applications for Windows.

Windows App SDK provides a unified set of APIs and tools to help you build beautiful & powerful Windows desktop apps. These APIs and tools can be used in a consistent way by any C++ Win32 or C# .NET app on a broad set of target Windows OS versions. WinAppSDK stays up to date with frequent, OS independent releases and supports the latest innovations in Windows app development – including .NET & Visual Studio.

Get started with Windows App SDK

To start using Windows App SDK, see Get started with Windows App SDK to set up your development environment and learn more about the components included in this release. If you want to jump right in with building your first WinUI 3 desktop app, start with our tutorial or watch our Learn Live session released at Build 2022.

Functionality introduced in Windows App SDK 1.2

Widgets for third-party applications

With the launch of Windows 11, we introduced the widgets board featuring content curated by Windows. Widgets provide a glanceable view of important information with one touch access from the taskbar or swipe from the left side of a touch screen and are populated by apps currently installed on the device. Now with the launch of Windows App SDK 1.2, we are excited to make this functionality available for third-party developers to create widgets for their packaged Win32 apps and test them locally on the Windows 11 widgets board through our Windows Insider Program.  By creating widgets for your apps, your customers can easily and seamlessly stay up to date with information that matters to them.

To get started developing Widgets for your app, check out the Widgets development docs and Widgets design fundamentals for prerequisites, guidance and best practices.

Latest WinUI controls including media playback

WinUI 3 apps can play audio and video with the MediaPlayerElement and MediaTransportControls media playback controls. For more info on how and when to use media controls, see Media players.

WinUI 3 has been updated with the latest controls, styles, and behaviors from WinUI 2.8. These updates include the addition of the InfoBadge control, improvements to accessibility and high contrast mode, as well as bug fixes across controls. For more details, see the release notes for WinUI 2.7 and WinUI 2.8.

Voice and video calling in WinUI 3 apps via Azure Communication Services (ACS)

You can now add voice and video calling capabilities to your WinUI 3 applications that run on Windows, enabling rich communication experiences for desktop PCs. Azure Communication Services use the same infrastructure, services, and technologies that power Microsoft Teams calling experiences.

Check out our conceptual documentation overview and try out quick starts and samples:

• Add voice calling to your WinUI 3 app
• Add 1:1 video calling to your WinUI 3 app

DisplayInformation

Windows desktop apps can now support High Dynamic Range (HDR) and Auto Color Management (ACM) through the DisplayInformation class in WinAppSDK. This API is easier to use than ever before for Win32 apps, and app developers can now use one API to target Windows version 1809  and later. The DisplayInformation class enables you to monitor display-related information for an application view. This includes events to allow clients to monitor for changes in the application view affecting which display(s) the view resides on, as well as changes in displays that can affect the application view.

Support for Visual Studio Arm64

As early as Project Reunion (now WinAppSDK) 0.5, apps developed with WinAppSDK were able to run on Arm64. Starting with Visual Studio 17.3 Preview 2, you will be able to natively develop applications with WinAppSDK on Arm64 devices.

To get started developing on an Arm64 device, check out our docs detailing Windows on Arm and Arm64 Visual Studio.

Trimming for .NET apps

You are now able to publish your .NET WinAppSDK apps trimmed. With CsWinRT 2.0, the C#/WinRT projections distributed in the WinAppSDK are trimmable. Publishing your app trimmed can reduce the disk footprint of your app by removing any unused code from trimmable binaries. Your app may also see a startup performance improvement. With a basic Hello World app, we have seen a ~80% disk footprint improvement and a ~7% startup performance improvement when published trimmed. With WinUI gallery, we have seen a ~45% disk footprint improvement.

For more details on how you can enable trimming, trimming limitations (such as reflection against trimmable types), and trim warnings, see Trim self-contained deployments and executables.

Dynamic Refresh Rate

Introduced in Windows 11, Dynamic Refresh Rate (DRR) enables devices to seamlessly switch between a lower refresh rate and a higher refresh rate based on what users are doing on their PC. This helps to balance performance and power consumption. As part of WinUI 3 in Windows App SDK 1.2, Microsoft.UI.Composition will now support Dynamic Refresh Rate on devices that opt-in to the feature. Notably, through supporting DRR, devices running Windows 22H2 will automatically have smoother scrolling and interactions in your app without any other changes.

To learn more about how to best support Dynamic Refresh Rate in your app, check out our Dynamic Refresh Rate Tool (built on WinAppSDK 1.1) which shows how to use the Compositor Clock API and support SwapChains.

AppNotificationBuilder

In Windows App SDK 1.1, we introduced the ability to create and send notifications from your application or a cloud service. App notifications can be used to inform the user of application status or state changes, or to prompt the user to take action with engaging and rich UI.

With WinAppSDK 1.2, we’re introducing the AppNotificationBuilder, an alternative to XML payload to simplify creating and defining these notifications. To get started using the AppNotificationBuilder to create app notifications, check out the AppNotificationBuilder spec on GitHub. Also see Quickstart: App notifications in the Windows App SDK for an example of how to create a desktop Windows application that sends and receives local app notifications.

Additional updates

Outside of the new functionality introduced in WinAppSDK 1.2, there are also several performance, reliability, and development experience improvements. Of note, the WinAppSDK 1.2 binary on x64 is 11% smaller than WinAppSDK 1.1.5.

Check out the release notes for the full list of fixed issues and updates in WinAppSDK 1.2.

Upcoming experiences on WinAppSDK

We are working with several development partners internal and external to Microsoft who are migrating their experiences to WinUI 3 and Windows App SDK. Stay tuned on our social channels for more information about these partnerships.

Staying in the loop

You can stay up to date with the team on the Windows App SDK GitHub repo and the WinUI GitHub repo, and through our monthly WinUI Community Calls where we share roadmap updates and other exciting news, and we demo new features.

You can also connect with us on Twitter using #WindowsAppSDK and @WindowsUI.

We look forward to seeing the beautiful apps you create with WinAppSDK 1.2 & WinUI 3!

Happy Coding!

Windows App SDK team