Skip to content

Commit 9b4da52

Browse files
author
Colin Robertson
authored
Merge pull request #1437 from msebolt/docset-changes-pr6
docset changes minor part3
2 parents 7648ed0 + 4a9321a commit 9b4da52

23 files changed

+126
-148
lines changed

‎docs/build/reference/delayload-delay-load-import.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,9 +31,9 @@ The [/DELAY](../../build/reference/delay-delay-load-import-settings.md) option s
3131

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

34-
2. In the **Linker** folder, select the **Input** property page.
34+
1. In the **Linker** folder, select the **Input** property page.
3535

36-
3. Modify the **Delay Loaded DLLs** property.
36+
1. Modify the **Delay Loaded DLLs** property.
3737

3838
### To set this linker option programmatically
3939

@@ -42,4 +42,4 @@ The [/DELAY](../../build/reference/delay-delay-load-import-settings.md) option s
4242
## See Also
4343

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

‎docs/build/reference/diagnostics-compiler-diagnostic-options.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -42,11 +42,11 @@ The **/diagnostics** option is available starting in Visual Studio 2017.
4242

4343
1. Open your project's **Property Pages** dialog box.
4444

45-
2. Under **Configuration Properties**, expand the **C/C++** folder and choose the **General** property page.
45+
1. Under **Configuration Properties**, expand the **C/C++** folder and choose the **General** property page.
4646

47-
3. Use the dropdown control in the **Diagnostics Format** field to select a diagnostics display option. Choose **OK** or **Apply** to save your changes.
47+
1. Use the dropdown control in the **Diagnostics Format** field to select a diagnostics display option. Choose **OK** or **Apply** to save your changes.
4848

4949
## See Also
5050

5151
[Compiler Options](../../build/reference/compiler-options.md)<br/>
52-
[Setting Compiler Options](../../build/reference/setting-compiler-options.md)
52+
[Setting Compiler Options](../../build/reference/setting-compiler-options.md)

‎docs/build/reference/export-exports-a-function.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -56,9 +56,9 @@ BOOL CALLBACK PlainFuncName( Things * lpParams)
5656
5757
1. Open the project's **Property Pages** dialog box. For details, see [Setting Visual C++ Project Properties](../../ide/working-with-project-properties.md).
5858
59-
2. Select the **Configuration Properties** > **Linker** > **Command Line** property page.
59+
1. Select the **Configuration Properties** > **Linker** > **Command Line** property page.
6060
61-
3. Enter the option into the **Additional Options** box.
61+
1. Enter the option into the **Additional Options** box.
6262
6363
### To set this linker option programmatically
6464

‎docs/build/reference/exports.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -71,11 +71,11 @@ There are four ways to export a definition, listed in recommended order:
7171

7272
1. The [__declspec(dllexport)](../../cpp/dllexport-dllimport.md) keyword in the source code
7373

74-
2. An `EXPORTS` statement in a .DEF file
74+
1. An `EXPORTS` statement in a .DEF file
7575

76-
3. An [/EXPORT](../../build/reference/export-exports-a-function.md) specification in a LINK command
76+
1. An [/EXPORT](../../build/reference/export-exports-a-function.md) specification in a LINK command
7777

78-
4. A [comment](../../preprocessor/comment-c-cpp.md) directive in the source code, of the form `#pragma comment(linker, "/export: definition ")`. The following example shows a #pragma comment directive before a function declaration, where `PlainFuncName` is the undecorated name, and `_PlainFuncName@4` is the decorated name of the function:
78+
1. A [comment](../../preprocessor/comment-c-cpp.md) directive in the source code, of the form `#pragma comment(linker, "/export: definition ")`. The following example shows a #pragma comment directive before a function declaration, where `PlainFuncName` is the undecorated name, and `_PlainFuncName@4` is the decorated name of the function:
7979

8080
```cpp
8181
#pragma comment(linker, "/export:PlainFuncName=_PlainFuncName@4")

‎docs/build/reference/fa-fa-listing-file.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -67,9 +67,9 @@ A listing file named *filename.extension* is placed in the specified *directory*
6767

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

70-
2. Select the **Configuration Properties** > **C/C++** > **Output Files** property page.
70+
1. Select the **Configuration Properties** > **C/C++** > **Output Files** property page.
7171

72-
3. Modify the **Assembler Output** property to set the **/FAc** and **/FAs** options for assembler, machine, and source code. Modify the **Use Unicode For Assembler Listing** property to set the **/FAu** option for ANSI or UTF-8 output. Modify the **ASM List Location** to set the **/Fa** option for listing file name and location.
72+
1. Modify the **Assembler Output** property to set the **/FAc** and **/FAs** options for assembler, machine, and source code. Modify the **Use Unicode For Assembler Listing** property to set the **/FAu** option for ANSI or UTF-8 output. Modify the **ASM List Location** to set the **/Fa** option for listing file name and location.
7373

7474
Note that setting both **Assembler Output** and **Use Unicode For Assembler Listing** properties can cause [Command-Line Warning D9025](../../error-messages/tool-errors/command-line-warning-d9025.md). To combine these options in the IDE, use the **Additional Options** field in the **Command Line** property page instead.
7575

@@ -90,4 +90,4 @@ CL /FAcs HELLO.CPP
9090
[Output-File (/F) Options](../../build/reference/output-file-f-options.md)<br/>
9191
[Compiler Options](../../build/reference/compiler-options.md)<br/>
9292
[Setting Compiler Options](../../build/reference/setting-compiler-options.md)<br/>
93-
[Specifying the Pathname](../../build/reference/specifying-the-pathname.md)
93+
[Specifying the Pathname](../../build/reference/specifying-the-pathname.md)

‎docs/build/reference/h-restrict-length-of-external-names.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -71,9 +71,9 @@ The **/H** option is deprecated since Visual Studio 2005; the maximum length lim
7171
7272
1. Open the project's **Property Pages** dialog box. For details, see [Working with Project Properties](../../ide/working-with-project-properties.md).
7373
74-
2. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
74+
1. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
7575
76-
3. Enter the compiler option in the **Additional Options** box.
76+
1. Enter the compiler option in the **Additional Options** box.
7777
7878
### To set this compiler option programmatically
7979
@@ -82,4 +82,4 @@ The **/H** option is deprecated since Visual Studio 2005; the maximum length lim
8282
## See Also
8383
8484
[Compiler Options](../../build/reference/compiler-options.md)<br/>
85-
[Setting Compiler Options](../../build/reference/setting-compiler-options.md)
85+
[Setting Compiler Options](../../build/reference/setting-compiler-options.md)

‎docs/build/reference/midl-specify-midl-command-line-options.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -35,9 +35,9 @@ The file should contain one MIDL command-line option per line.
3535

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

38-
2. Select the **Configuration Properties** > **Linker** > **Embedded IDL** property page.
38+
1. Select the **Configuration Properties** > **Linker** > **Embedded IDL** property page.
3939

40-
3. Modify the **MIDL Commands** property.
40+
1. Modify the **MIDL Commands** property.
4141

4242
### To set this linker option programmatically
4343

@@ -50,4 +50,4 @@ The file should contain one MIDL command-line option per line.
5050
[/IDLOUT (Name MIDL Output Files)](../../build/reference/idlout-name-midl-output-files.md)<br/>
5151
[/IGNOREIDL (Don't Process Attributes into MIDL)](../../build/reference/ignoreidl-don-t-process-attributes-into-midl.md)<br/>
5252
[/TLBOUT (Name .TLB File)](../../build/reference/tlbout-name-dot-tlb-file.md)<br/>
53-
[Building an Attributed Program](../../windows/building-an-attributed-program.md)
53+
[Building an Attributed Program](../../windows/building-an-attributed-program.md)

‎docs/build/struct-unwind-code.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -103,17 +103,17 @@ This unwind code will always appear in a dummy prolog, which is never actually e
103103

104104
1. Pop RIP return address from top of stack into *Temp*
105105

106-
2. Push SS
106+
1. Push SS
107107

108-
3. Push old RSP
108+
1. Push old RSP
109109

110-
4. Push EFLAGS
110+
1. Push EFLAGS
111111

112-
5. Push CS
112+
1. Push CS
113113

114-
6. Push *Temp*
114+
1. Push *Temp*
115115

116-
7. Push Error Code (if op info equals 1)
116+
1. Push Error Code (if op info equals 1)
117117

118118
The simulated `UWOP_PUSH_MACHFRAME` operation decrements RSP by 40 (op info equals 0) or 48 (op info equals 1).
119119

@@ -135,4 +135,4 @@ The meaning of these 4 bits depends upon the operation code. To encode a general
135135

136136
## See Also
137137

138-
[Unwind Data for Exception Handling, Debugger Support](../build/unwind-data-for-exception-handling-debugger-support.md)
138+
[Unwind Data for Exception Handling, Debugger Support](../build/unwind-data-for-exception-handling-debugger-support.md)

‎docs/build/walkthrough-compile-a-c-program-on-the-command-line.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Before you can build a C or C++ program on the command line, you must verify tha
3737

3838
If you're using a different version of Visual Studio or are running a different version of Windows, look in your Start menu or Start page for a Visual Studio tools folder that contains a developer command prompt shortcut. You can also use the Windows search function to search for "developer command prompt" and choose one that matches your installed version of Visual Studio. Use the shortcut to open the command prompt window.
3939

40-
1. Next, verify that the Visual C++ developer command prompt is set up correctly. In the command prompt window, enter `cl` and verify that the output looks something like:
40+
1. Next, verify that the Visual C++ developer command prompt is set up correctly. In the command prompt window, enter `cl` and verify that the output looks something like this:
4141

4242
```Output
4343
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise>cl

‎docs/build/walkthrough-compiling-a-native-cpp-program-on-the-command-line.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Before you can build a C or C++ program on the command line, you must verify tha
4040

4141
If you're using a different version of Visual Studio or are running a different version of Windows, look in your Start menu or Start page for a Visual Studio tools folder that contains a developer command prompt shortcut. You can also use the Windows search function to search for "developer command prompt" and choose one that matches your installed version of Visual Studio. Use the shortcut to open the command prompt window.
4242

43-
1. Next, verify that the Visual C++ developer command prompt is set up correctly. In the command prompt window, enter `cl` and verify that the output looks something like:
43+
1. Next, verify that the Visual C++ developer command prompt is set up correctly. In the command prompt window, enter `cl` and verify that the output looks something like this:
4444

4545
```Output
4646
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise>cl
@@ -127,7 +127,7 @@ Before you can build a C or C++ program on the command line, you must verify tha
127127
> [!NOTE]
128128
> If you get a different compiler or linker error or warning, review your source code to correct any errors, then save it and run the compiler again. For information about specific errors, use the search box on this MSDN page to look for the error number.
129129
130-
7. To run the hello.exe program, at the command prompt, enter `hello`.
130+
1. To run the hello.exe program, at the command prompt, enter `hello`.
131131

132132
The program displays this text and exits:
133133

0 commit comments

Comments
 (0)