Skip to content

Commit 2bebe2e

Browse files
nxtnnxtn
committed
Standardize See also sections
1 parent 8cdf91f commit 2bebe2e

File tree

446 files changed

+854
-855
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

446 files changed

+854
-855
lines changed

‎docs/build/active-technology-and-dlls.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,6 @@ If you are writing an Automation server and your server has no user interface, y
1414

1515
- [Automation Servers](../mfc/automation-servers.md)
1616

17-
## See Also
17+
## See also
1818

19-
[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)
19+
[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)

‎docs/build/automation-in-a-dll.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,6 @@ When you choose the Automation option in the MFC DLL Wizard, the wizard provides
2222

2323
- [Automation Servers](../mfc/automation-servers.md)
2424

25-
## See Also
25+
## See also
2626

27-
[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)
27+
[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)

‎docs/build/batch-mode-rules.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,6 @@ foo4.cpp
8080
Generating Code...
8181
```
8282

83-
## See Also
83+
## See also
8484

85-
[Inference Rules](../build/inference-rules.md)
85+
[Inference Rules](../build/inference-rules.md)

‎docs/build/build-system-changes.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,6 @@ You cannot change the VC++ directories settings if you run [devenv /resetsetting
5858

5959
Migrate VC++ directories settings from a .vssettings file that is created by an earlier release of Visual C++. Open the **Tools** menu, click **Import and Export Settings**, select **Import selected environment settings**, and then follow the directions in the wizard. Or when you start Visual Studio for the first time, on the **Choose Default Environment Settings** dialog box, select **Migrate my eligible settings from a previous version and apply them in addition to the default settings selected below**.
6060

61-
## See Also
61+
## See also
6262

63-
[MSBuild (Visual C++)](../build/msbuild-visual-cpp.md)
63+
[MSBuild (Visual C++)](../build/msbuild-visual-cpp.md)

‎docs/build/building-c-cpp-isolated-applications.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ An isolated application depends only on side-by-side assemblies and binds to its
1010

1111
When you build your native C/C++ application using Visual C++, by default the Visual Studio project system generates a manifest file that describes your application's dependencies on Visual C++ libraries. If these are the only dependencies your application has, then it becomes an isolated application as soon as it is rebuilt with Visual Studio. If your application is using other libraries at runtime, then you may need to rebuild those libraries as side-by-side assemblies following the steps described in [Building C/C++ Side-by-side Assemblies](../build/building-c-cpp-side-by-side-assemblies.md).
1212

13-
## See Also
13+
## See also
1414

1515
[Concepts of Isolated Applications and Side-by-side Assemblies](../build/concepts-of-isolated-applications-and-side-by-side-assemblies.md)<br/>
16-
[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)
16+
[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)

‎docs/build/building-c-cpp-side-by-side-assemblies.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,8 @@ One or several related DLLs can be repackaged into a side-by-side assembly with
2222
2323
This change may allow deployment of corresponding DLLs as a [private assembly](/windows/desktop/Msi/private-assemblies) in an application local folder or as a [shared assembly](/windows/desktop/Msi/shared-assemblies) in the WinSxS assembly cache. Several steps have to be followed in order to achieve correct runtime behavior of this new assembly; they are described in [Guidelines for Creating Side-by-side Assemblies](/windows/desktop/SbsCs/guidelines-for-creating-side-by-side-assemblies). After an assembly is correctly authored it can deployed as either a shared or private assembly together with an application that depends on it. When installing side-by-side assemblies as a shared assembly, you may either follow the guidelines outlined in [Installing Win32 Assemblies for Side-by-Side Sharing on Windows XP](/windows/desktop/Msi/installing-win32-assemblies-for-side-by-side-sharing-on-windows-xp) or use [merge modules](/windows/desktop/msi/merge-modules). When installing side-by-side assemblies as a private assembly, you may just copy the corresponding DLL, resources and assembly manifest as part of the installation process to the application local folder on the target computer, ensuring that this assembly can be found by the loader at runtime (see [Assembly Searching Sequence](/windows/desktop/SbsCs/assembly-searching-sequence)). Another way is to use [Windows Installer](/windows/desktop/Msi/windows-installer-portal) and follow the guidelines outlined in [Installing Win32 Assemblies for the Private Use of an Application on Windows XP](/windows/desktop/Msi/installing-win32-assemblies-for-the-private-use-of-an-application-on-windows-xp).
2424

25-
## See Also
25+
## See also
2626

2727
[Deployment Examples](../ide/deployment-examples.md)<br/>
2828
[Building C/C++ Isolated Applications](../build/building-c-cpp-isolated-applications.md)<br/>
29-
[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)
29+
[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)

‎docs/build/calling-dll-functions-from-visual-basic-applications.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,6 @@ For DLLs to be called by programs written in Visual Basic, the alias technique s
5757

5858
- [Decorated names](../build/reference/decorated-names.md)
5959

60-
## See Also
60+
## See also
6161

6262
[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)

‎docs/build/command-macros-and-options-macros.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,6 @@ Command macros are predefined for Microsoft products. Options macros represent o
1717
|C++ Compiler|**CXX**|cl|**CXXFLAGS**|
1818
|Resource Compiler|**RC**|rc|**RFLAGS**|
1919

20-
## See Also
20+
## See also
2121

22-
[Special NMAKE Macros](../build/special-nmake-macros.md)
22+
[Special NMAKE Macros](../build/special-nmake-macros.md)

‎docs/build/command-modifiers.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,6 @@ You can specify one or more command modifiers preceding a command, optionally se
1414
|**-**\[*number*] *command*|Turns off error checking for *command*. By default, NMAKE halts when a command returns a nonzero exit code. If -*number* is used, NMAKE stops if the exit code exceeds *number*. Spaces or tabs cannot appear between the dash and *number.* At least one space or tab must appear between `number` and *command*. Use /I to turn off error checking for the entire makefile; use **.IGNORE** to turn off error checking for part of the makefile.|
1515
|**!** *command*|Executes *command* for each dependent file if *command* uses <strong>$\*\*</strong> (all dependent files in the dependency) or **$?** (all dependent files in the dependency with a later timestamp than the target).|
1616

17-
## See Also
17+
## See also
1818

1919
[Commands in a Makefile](../build/commands-in-a-makefile.md)

‎docs/build/commands-in-a-makefile.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,6 @@ project.obj : project.c project.h ; cl /c project.c
2626

2727
[Inline files in a makefile](../build/inline-files-in-a-makefile.md)
2828

29-
## See Also
29+
## See also
3030

31-
[NMAKE Reference](../build/nmake-reference.md)
31+
[NMAKE Reference](../build/nmake-reference.md)

‎docs/build/comments-in-a-makefile.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,6 @@ To specify a literal number sign, precede it with a caret (**^**), as follows:
3232
DEF = ^#define #Macro for a C preprocessing directive
3333
```
3434

35-
## See Also
35+
## See also
3636

37-
[Contents of a Makefile](../build/contents-of-a-makefile.md)
37+
[Contents of a Makefile](../build/contents-of-a-makefile.md)

‎docs/build/common-visual-cpp-64-bit-migration-issues.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ For more information, see:
3030

3131
- [Migration Tips](/windows/desktop/WinProg64/migration-tips)
3232

33-
## See Also
33+
## See also
3434

3535
[Configure Visual C++ for 64-bit, x64 targets](../build/configuring-programs-for-64-bit-visual-cpp.md)<br/>
36-
[Visual C++ Porting and Upgrading Guide](../porting/visual-cpp-porting-and-upgrading-guide.md)
36+
[Visual C++ Porting and Upgrading Guide](../porting/visual-cpp-porting-and-upgrading-guide.md)

‎docs/build/concepts-of-isolated-applications-and-side-by-side-assemblies.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,6 @@ You can change side-by-side assembly dependencies after an application has been
2626

2727
In Visual Studio 2005 and Visual Studio 2008, redistributable libraries such as ATL, MFC, CRT, Standard C++, OpenMP, and MSDIA were deployed as shared side-by-side assemblies to the native assembly cache. In the current version, the redistributable libraries use central deployment. By default, all applications that are built by using Visual C++ are built with the manifest embedded in the final binary, and the manifest describes the dependencies of the binary on the Visual C++ libraries. To understand manifest generation for Visual C++ applications, see [Understanding Manifest Generation for C/C++ Programs](../build/understanding-manifest-generation-for-c-cpp-programs.md). A manifest is not required for applications that are statically linked to the libraries that they use, or that use local deployment. For more information about deployment, see [Deployment in Visual C++](../ide/deployment-in-visual-cpp.md).
2828

29-
## See Also
29+
## See also
3030

31-
[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)
31+
[Building C/C++ Isolated Applications and Side-by-side Assemblies](../build/building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)

‎docs/build/configuring-programs-for-64-bit-visual-cpp.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,6 @@ This section contains topics about targeting 64-bit x64 hardware with the Visual
3434

3535
[x64 (amd64) Intrinsics List](../intrinsics/x64-amd64-intrinsics-list.md)
3636

37-
## See Also
37+
## See also
3838

39-
[Building C/C++ Programs](building-c-cpp-programs.md)
39+
[Building C/C++ Programs](building-c-cpp-programs.md)

‎docs/build/contents-of-a-makefile.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,6 @@ Other features you can use in a makefile are [wildcards](../build/wildcards-and-
2626

2727
For a sample, see [Sample Makefile](../build/sample-makefile.md).
2828

29-
## See Also
29+
## See also
3030

31-
[NMAKE Reference](../build/nmake-reference.md)
31+
[NMAKE Reference](../build/nmake-reference.md)

‎docs/build/creating-a-resource-only-dll.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ The application that uses the resource-only DLL should call [LoadLibrary](../bui
3838

3939
The application should call `FreeLibrary` when it is finished using the resources.
4040

41-
## See Also
41+
## See also
4242

4343
[Working with Resource Files](../windows/working-with-resource-files.md)<br/>
44-
[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)
44+
[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)

‎docs/build/creating-inline-file-text.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,6 @@ Specify *inlinetext* on the first line after the command. Mark the end with doub
2424

2525
A temporary file exists for the duration of the session and can be reused by other commands. Specify **KEEP** after the closing angle brackets to retain the file after the NMAKE session; an unnamed file is preserved on disk with the generated filename. Specify **NOKEEP** or nothing for a temporary file. **KEEP** and **NOKEEP** are not case sensitive.
2626

27-
## See Also
27+
## See also
2828

29-
[Inline Files in a Makefile](../build/inline-files-in-a-makefile.md)
29+
[Inline Files in a Makefile](../build/inline-files-in-a-makefile.md)

‎docs/build/cumulative-dependencies.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,6 @@ climb.exe : up.obj
4545
echo Building bounce.exe...
4646
```
4747

48-
## See Also
48+
## See also
4949

50-
[Targets](../build/targets.md)
50+
[Targets](../build/targets.md)

‎docs/build/defining-a-rule.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,6 @@ Extensions are not case sensitive. Macros can be invoked to represent *fromext*
2121

2222
[Search paths in rules](../build/search-paths-in-rules.md)
2323

24-
## See Also
24+
## See also
2525

26-
[Inference Rules](../build/inference-rules.md)
26+
[Inference Rules](../build/inference-rules.md)

‎docs/build/defining-an-nmake-macro.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,6 @@ The `string` can be any sequence of zero or more characters. A null string conta
2929

3030
[Precedence in macro definitions](../build/precedence-in-macro-definitions.md)
3131

32-
## See Also
32+
## See also
3333

34-
[Macros and NMAKE](../build/macros-and-nmake.md)
34+
[Macros and NMAKE](../build/macros-and-nmake.md)

‎docs/build/dependency-side-effects.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,6 @@ bounce.exe : up.obj
4141
# invokes an inference rule
4242
```
4343

44-
## See Also
44+
## See also
4545

46-
[Targets](../build/targets.md)
46+
[Targets](../build/targets.md)

‎docs/build/dependents.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,6 @@ In a dependency line, specify zero or more dependents after the colon (:) or dou
1414

1515
[Search paths for dependents](../build/search-paths-for-dependents.md)
1616

17-
## See Also
17+
## See also
1818

19-
[Description Blocks](../build/description-blocks.md)
19+
[Description Blocks](../build/description-blocks.md)

‎docs/build/description-blocks.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,6 @@ A dependency line specifies one or more targets and zero or more dependents. A t
2121

2222
[Dependents](../build/dependents.md)
2323

24-
## See Also
24+
## See also
2525

26-
[NMAKE Reference](../build/nmake-reference.md)
26+
[NMAKE Reference](../build/nmake-reference.md)

‎docs/build/determining-which-exporting-method-to-use.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,6 @@ Using `__declspec(dllexport)` is convenient because you do not have to worry abo
5050

5151
- [Decorated names](../build/reference/decorated-names.md)
5252

53-
## See Also
53+
## See also
5454

55-
[Exporting from a DLL](../build/exporting-from-a-dll.md)
55+
[Exporting from a DLL](../build/exporting-from-a-dll.md)

‎docs/build/dll-frequently-asked-questions.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,6 @@ DLLs that are implicitly linked to an application are loaded when the applicatio
5858

5959
One possible cause of the memory leak is that MFC creates temporary objects that are used inside message handler functions. In MFC applications, these temporary objects are automatically cleaned up in the `CWinApp::OnIdle()` function that is called in between processing messages. However, in MFC dynamic-link libraries (DLLs), the `OnIdle()` function is not automatically called. As a result, temporary objects are not automatically cleaned up. To clean up temporary objects, the DLL must explicitly call `OnIdle(1)` periodically.
6060

61-
## See Also
61+
## See also
6262

63-
[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)
63+
[DLLs in Visual C++](../build/dlls-in-visual-cpp.md)

‎docs/build/dot-directives.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,6 @@ To add additional suffixes to the end of the list, specify
2929

3030
where *suffixlist* is a list of the additional suffixes, separated by one or more spaces or tabs. To see the current setting of **.SUFFIXES**, run NMAKE with /P.
3131

32-
## See Also
32+
## See also
3333

34-
[NMAKE Reference](../build/nmake-reference.md)
34+
[NMAKE Reference](../build/nmake-reference.md)

‎docs/build/environment-variable-macros.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,6 @@ In this example, changing `PATH` changes the corresponding environment variable
2323

2424
If an environment variable is defined as a string that would be syntactically incorrect in a makefile, no macro is created and no warning is generated. If a variable's value contains a dollar sign ($), NMAKE interprets it as the beginning of a macro invocation. Using the macro can cause unexpected behavior.
2525

26-
## See Also
26+
## See also
2727

28-
[Special NMAKE Macros](../build/special-nmake-macros.md)
28+
[Special NMAKE Macros](../build/special-nmake-macros.md)

‎docs/build/exception-handling-x64.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -494,6 +494,6 @@ typedef struct _RUNTIME_FUNCTION {
494494
((PVOID)((PULONG)GetLanguageSpecificData(info) + 1)
495495
```
496496
497-
## See Also
497+
## See also
498498
499-
[x64 software conventions](../build/x64-software-conventions.md)
499+
[x64 software conventions](../build/x64-software-conventions.md)

‎docs/build/executing-a-program-in-preprocessing.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,6 @@ ms.assetid: 5ecf123a-20e5-40cd-b8d8-dd5a9fdd4b24
88

99
To use a command's exit code during preprocessing, specify the command, with any arguments, within brackets ([ ]). Any macros are expanded before the command is executed. NMAKE replaces the command specification with the command's exit code, which can be used in an expression to control preprocessing.
1010

11-
## See Also
11+
## See also
1212

13-
[Expressions in Makefile Preprocessing](../build/expressions-in-makefile-preprocessing.md)
13+
[Expressions in Makefile Preprocessing](../build/expressions-in-makefile-preprocessing.md)

‎docs/build/exit-codes-from-nmake.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,6 @@ NMAKE returns the following exit codes:
1919
|4|System error — out of memory|
2020
|255|Target is not up-to-date (issued only when /Q is used)|
2121

22-
## See Also
22+
## See also
2323

24-
[Running NMAKE](../build/running-nmake.md)
24+
[Running NMAKE](../build/running-nmake.md)

‎docs/build/exporting-and-importing-using-afx-ext-class.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -113,6 +113,6 @@ Because MFC always uses the `AFX_DATA` symbol on data items it defines within it
113113

114114
- [Mutual imports](../build/mutual-imports.md)
115115

116-
## See Also
116+
## See also
117117

118-
[Exporting from a DLL](../build/exporting-from-a-dll.md)
118+
[Exporting from a DLL](../build/exporting-from-a-dll.md)

‎docs/build/exporting-c-functions-for-use-in-c-or-cpp-language-executables.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,6 @@ extern "C" {
5353

5454
- [Using extern to Specify Linkage](../cpp/using-extern-to-specify-linkage.md)
5555

56-
## See Also
56+
## See also
5757

58-
[Exporting from a DLL](../build/exporting-from-a-dll.md)
58+
[Exporting from a DLL](../build/exporting-from-a-dll.md)

‎docs/build/exporting-cpp-functions-for-use-in-c-language-executables.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,6 @@ extern "C" __declspec( dllexport ) int MyFunc(long parm1);
3636

3737
- [Using extern to Specify Linkage](../cpp/using-extern-to-specify-linkage.md)
3838

39-
## See Also
39+
## See also
4040

41-
[Exporting from a DLL](../build/exporting-from-a-dll.md)
41+
[Exporting from a DLL](../build/exporting-from-a-dll.md)

‎docs/build/exporting-from-a-dll-using-declspec-dllexport.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,6 @@ As a reference, search through the Win32 Winbase.h header file. It contains exam
6868

6969
- [Mutual imports](../build/mutual-imports.md)
7070

71-
## See Also
71+
## See also
7272

73-
[Exporting from a DLL](../build/exporting-from-a-dll.md)
73+
[Exporting from a DLL](../build/exporting-from-a-dll.md)

‎docs/build/exporting-from-a-dll-using-def-files.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -73,6 +73,6 @@ Note that MFC itself uses DEF files to export functions and classes from the MFC
7373

7474
- [Mutual imports](../build/mutual-imports.md)
7575

76-
## See Also
76+
## See also
7777

78-
[Exporting from a DLL](../build/exporting-from-a-dll.md)
78+
[Exporting from a DLL](../build/exporting-from-a-dll.md)

‎docs/build/exporting-from-a-dll.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,6 @@ When exporting functions with either method, make sure to use the [__stdcall](..
4444

4545
- [Mutual imports](../build/mutual-imports.md)
4646

47-
## See Also
47+
## See also
4848

49-
[Importing and Exporting](../build/importing-and-exporting.md)
49+
[Importing and Exporting](../build/importing-and-exporting.md)

‎docs/build/exporting-functions-from-a-dll-by-ordinal-rather-than-by-name.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,6 @@ The simplest way to export functions from your DLL is to export them by name. Th
1818

1919
- [Use __declspec(dllexport)](../build/exporting-from-a-dll-using-declspec-dllexport.md)
2020

21-
## See Also
21+
## See also
2222

23-
[Exporting from a DLL](../build/exporting-from-a-dll.md)
23+
[Exporting from a DLL](../build/exporting-from-a-dll.md)

‎docs/build/expressions-in-makefile-preprocessing.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,6 @@ Expressions can use operators that act on constant values, exit codes from comma
1616

1717
[Executing a program in preprocessing](../build/executing-a-program-in-preprocessing.md)
1818

19-
## See Also
19+
## See also
2020

21-
[Makefile Preprocessing](../build/makefile-preprocessing.md)
21+
[Makefile Preprocessing](../build/makefile-preprocessing.md)

‎docs/build/extension-dlls-overview.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,6 @@ Note that the term AFXDLL is no longer used in the Visual C++ documentation. An
3232

3333
- [Creating an MFC DLL](../mfc/reference/mfc-dll-wizard.md)
3434

35-
## See Also
35+
## See also
3636

37-
[Kinds of DLLs](../build/kinds-of-dlls.md)
37+
[Kinds of DLLs](../build/kinds-of-dlls.md)

0 commit comments

Comments
 (0)