The Windows API, informally WinAPI, is Microsoft's
core set of application programming interfaces (APIs) available in the Microsoft Windows operating systems. It was formerly called the
Win32 API; however, the name "Windows API" more accurately reflects its roots in 16-bit Windows and its support in 64-bit Windows. Almost all Windows programs interact with the Windows API; on the Windows NT line of OSes, a small number (such
as programs started early in the Windows startup process) use the Native API.
The Windows API is used by every software developer who wants to build applications that target the Windows operating system. In the past, where Windows development was mainly message driven, the developer had to manually write the code that created the window,
set up the message processing loop, and react to every user action by receiving messages from the operating system. For example, WM_LBUTTONDOWN tells us that the user has clicked the left mouse button, while WM_PAINT tells the window procedure that the window's
client area has changed and must be repainted. The modern integrated development environments (IDEs) hide the complexity of such a programming approach by allowing developers to graphically create the user interface of their applications, following the
Rapid Application Development (RAD) paradigm.
Writing every single line of code is not practical and leads to a waste of time, so many software companies developed packages that wrap the big set of Windows APIs in more compact and usable
class libraries that simplify the developers' work. For example, Borland introduced the
Object Windows Library (OWL), while Microsoft developed the
Microsoft Foundation Class (MFC). Today there is the Microsoft .NET Framework.
The large set of libraries and functions that constitute the API are provided to software developers by the
Software Development Kit (SDK, also known as Platform SDK), along with a complete set of tools (like compilers and linkers).
The Native API (with capitalized N) is the mostly undocumented application programming interface used internally by the Windows NT family of Windows operating systems. It is predominately used
during system boot, when other components of Windows are unavailable. The program entry point is called
DriverEntry(), the same as for a Windows Device Driver. However, the application runs in Ring 3 the same as a regular Windows Application. Most of the Native API calls are
implemented in ntoskrnl.exe and are exposed to user mode by
ntdll.dll. Some Native API calls are implemented in user mode directly within
While most of Microsoft Windows is implemented using the documented and well-defined Windows API, a few components, such as the Client/Server Runtime Subsystem, are implemented using the Native API, as they can be started earlier in the Windows NT Startup Process
when the Windows API is not yet available.
NOTE: the following links are external to the TechNet Wiki.
This article was written by
This article is also available in the following languages:
Thanks for the credits, Ed.
This page could be added to the MSDN Wiki (if that project is still alive).
Is there a TechNet API? If so, where is the documentation for it?
A TechNet API? What should it be aimed at, Rich? Provide me with more details about your question, I'll perform some search.
Just adding tags. I started the "Multi Language Wiki Articles" tag so that we can track what's been hand-translated into multiple languages. Thanks!
That's a useful tag, Ed.
What about the "EAA" and "ESAS" tags? What do they stand for?
I would also like to know what meant about "EAA" and "ESAS".
I believe there is..