`__stdcall` creates the correct calling convention for the function (the called function cleans up the stack and parameters are passed from right to left) but decorates the function name differently. So, when **__declspec(dllexport)** is used on an exported function in a DLL, the decorated name is exported.

int __stdcall func (int a, double b)

Each of the three build events is represented in an item definition group by a command element (`<Command>`) that is executed and a message element (`<Message>`) that is displayed when **MSBuild** performs the build event. Each element is optional, and if you specify the same element multiple times, the last occurrence takes precedence.

The following table lists each build event XML element:

Unless you plan to explicitly call `_penter`, you do not need to provide a prototype. The function must appear as if it had the following prototype, and it must push the content of all registers on entry and pop the unchanged content on exit:

This declaration is not available for 64-bit projects.

The following code, when compiled with **/Gh**, shows how `_penter` is called twice; once when entering function `main` and once when entering function `x`.

x();

}

_asm {

push eax

push ebx

Unless you plan to explicitly call `_pexit`, you do not need to provide a prototype. The function must appear as if it had the following prototype, and it must push the content of all registers on entry and pop the unchanged content on exit:

`_pexit` is similar to `_penter`; see [/Gh (Enable _penter Hook Function)](../../build/reference/gh-enable-penter-hook-function.md) for an example of how to write a `_pexit` function.

One of *asInvoker*, *highestAvailable*, or *requireAdministrator*. Defaults to asInvoker. For more information, see the Remarks section later in this topic.

*_uiAccess*<br/>

- [__assume](../../intrinsics/assume.md)

- [#pragma auto_inline](../../preprocessor/auto-inline.md)

Enables generation of a Windows Runtime Metadata (.winmd) file.

**/WINMD**<br/>

The default setting for Universal Windows Platform apps. The linker generates both the binary executable file and the .winmd metadata file.

**/WINMD:ONLY**<br/>

The linker generates only the .winmd file, but not the binary executable file.

1. Open the project's **Property Pages** dialog box. For details, see [Working with Project Properties](../../ide/working-with-project-properties.md).

1. In the **Generate Windows Metadata** drop-down list box, select the option you want.

[Setting Linker Options](../../build/reference/setting-linker-options.md)<br/>

title: "C Keywords | Microsoft Docs"

ms.custom: ""

ms.technology: ["cpp-language"]

ms.topic: "language-reference"

dev_langs: ["C++"]

|-|-|-|-|

¹ The **__based** keyword has limited uses for 32-bit and 64-bit target compilations.

² These are special identifiers when used with **__declspec**; their use in other contexts is not restricted.

When Microsoft extensions are enabled, you can use the keywords listed above in your programs. For ANSI compliance, most of these keywords are prefaced by a double underscore. The four exceptions, **dllexport**, **dllimport**, **naked**, and **thread**, are used only with **__declspec** and therefore do not require a leading double underscore. For backward compatibility, single-underscore versions of the rest of the keywords are supported.