| Platform SDK: Exchange Server |
In each description for the sample, an introduction is provided indicating what the sample covers and how it can be used. Next, for command-line samples, a syntax diagram is provided, as well as a list of required parameters, optional parameters, and descriptions. The syntax diagram shows the conventions that are followed.
| Convention | Description |
|---|---|
Sample Text |
This text represents literal expressions that must be typed exactly as shown, such as function names, structure names, and keywords. It also is used when giving examples that should be typed exactly as shown. For example,
regsvr32.exe acl.dll |
| [ ] | Brackets enclose optional syntax items. Type only the syntax within the brackets, not the brackets themselves. For example [/HELP or /?] means that these flags are optional for a particular command-line sample. |
| Bold Text | Bold text is used to outline selection options for applications like Microsoft Visual Studio. It is also used to label function, COM class, and interface names. For example, Build->Build ACL.dll (F7) and AcctCrt COM class. |
Tip When using parameters for the Microsoft Exchange Server sample applications, you need not type the entire parameter on the command line. You can enter the minimum number of characters necessary to unambiguously identify a command-line flag. For example, /C= is enough to identify the /CONTAINER= flag, but /IMP= is not enough to distinguish between the /IMPORT, /IMPLINE and /IMPFILE flags. Command-line parameters can be started with either a slash ("/") or dash ("-") character.
Finally, additional material is presented that discusses using the sample where appropriate.