Skip to content

Commit bb7b833

Browse files
author
mikeblome
committed
fixed links
1 parent 31f742b commit bb7b833

37 files changed

Lines changed: 51 additions & 55 deletions

‎docs/atl/reference/creating-an-atl-project.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ The easiest way to create an ATL project is to use the ATL Project Wizard, locat
1111

1212
## To create an ATL project using the ATL Project Wizard
1313

14-
1. Follow the instructions in the topic [Creating a Project with a Visual C++ Application Wizard](../../build/creating-desktop-projects-by-using-application-wizards.md).
14+
1. In Visual Studio, choose **File > New > Project** from the main menu.
1515

1616
1. Select the **ATL Project** icon in the **Templates** pane to open the **ATL Project Wizard**.
1717

‎docs/build/creating-and-managing-visual-cpp-projects.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ A *Visual Studio project* is a project based on the MSBuild build system. MSBuil
1313

1414
You can create C++ projects by choosing **File | New | Project**, then choosing Visual C++ in the left pane. In the center pane you see a list of project templates:
1515

16-
![Project Templates](../ide/media/vs2017-new-project.png "Visual Studio 2017 New Project Dialog")
16+
![Project Templates](media/vs2017-new-project.png "Visual Studio 2017 New Project Dialog")
1717

1818
For more information about all the default project templates that are included in Visual Studio, see [C++ project templates in Visual Studio](reference/visual-cpp-project-types.md). You can create your own project templates. For more information, see [How to: Create project templates](/visualstudio/ide/how-to-create-project-templates).
1919

@@ -41,7 +41,7 @@ To compile and run the new project, press **F5** or click the *debug dropdown* w
4141

4242
A new project compiles without errors. When adding your own code, you may occasionally introduce an error or trigger a warning. An error prevents the build from completing; a warning does not. All errors and warnings will appear both in the Output Window and in the Error List when you build the project.
4343

44-
![Output window and error list](../ide/media/vs2017-output-error-list.png) "Visual Studio 2017 error List")
44+
![Output window and error list](media/vs2017-output-error-list.png) "Visual Studio 2017 error List")
4545

4646
In the Error List, you can press **F1** on a highlighted error to go to its documentation topic.
4747

docs/ide/media/open-folder-add-config.png renamed to docs/build/media/open-folder-add-config.png

File renamed without changes.

docs/ide/media/open-folder-intellisense-mode.png renamed to docs/build/media/open-folder-intellisense-mode.png

File renamed without changes.

docs/build/reference/media/vc30ow1.gif renamed to docs/build/media/vc30ow1.gif

File renamed without changes.

‎docs/build/reference/advanced-manifest-tool.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Advanced, Manifest Tool, Configuration Properties, \<Projectname> Property Pages Dialog Box"
2+
title: "Advanced, Manifest Tool, Configuration Properties, &lt;Projectname> Property Pages Dialog Box"
33
ms.date: "11/04/2016"
44
f1_keywords: ["VC.Project.VCManifestTool.KeyFile", "VC.Project.VCManifestTool.UpdateFileHashes", "VC.Project.VCManifestTool.UpdateFileHashesSearchPath", "VC.Project.VCManifestTool.ValidateSignature", "VC.Project.VCManifestTool.KeyContainer"]
55
ms.assetid: 3d587366-05ea-4956-a978-313069660735

‎docs/build/reference/cetcompat.md‎

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ The **/CETCOMPAT** option is available beginning in the Visual Studio 2019 Previ
2727

2828
### To set the /CETCOMPAT linker option in Visual Studio
2929

30-
1. Open the **Property Pages** dialog box for the project. For more information, see [Working with Project Properties](../../ide/working-with-project-properties.md).
30+
1. Open the **Property Pages** dialog box for the project. For more information, see [Working with Project Properties](../working-with-project-properties.md).
3131

3232
1. Select the **Configuration Properties** > **Linker** > **Command Line** property page.
3333

@@ -39,5 +39,4 @@ This option does not have a programmatic equivalent.
3939

4040
## See also
4141

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

‎docs/build/reference/cl-command-files.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@ ms.assetid: ec3cea06-2af0-4fe9-a94c-119c9d31b3a9
77
---
88
# CL Command Files
99

10-
A command file is a text file that contains options and filenames you would otherwise type on the [command line](compiler-command-line-syntax.md) or specify using the [CL environment variable](reference/cl-environment-variables.md). CL accepts a compiler command file as an argument in the CL environment variable or on the command line. Unlike either the command line or the CL environment variable, a command file allows you to use multiple lines of options and filenames.
10+
A command file is a text file that contains options and filenames you would otherwise type on the [command line](compiler-command-line-syntax.md) or specify using the [CL environment variable](cl-environment-variables.md). CL accepts a compiler command file as an argument in the CL environment variable or on the command line. Unlike either the command line or the CL environment variable, a command file allows you to use multiple lines of options and filenames.
1111

12-
Options and filenames in a command file are processed according to the location of a command filename within the CL environment variable or on the command line. However, if the /link option appears in the command file, all options on the rest of the line are passed to the linker. Options in subsequent lines in the command file and options on the command line after the command file invocation are still accepted as compiler options. For more information on how the order of options affects their interpretation, see [Order of CL Options](reference/order-of-cl-options.md).
12+
Options and filenames in a command file are processed according to the location of a command filename within the CL environment variable or on the command line. However, if the /link option appears in the command file, all options on the rest of the line are passed to the linker. Options in subsequent lines in the command file and options on the command line after the command file invocation are still accepted as compiler options. For more information on how the order of options affects their interpretation, see [Order of CL Options](order-of-cl-options.md).
1313

1414
A command file must not contain the CL command. Each option must begin and end on the same line; you cannot use the backslash (**\\**) to combine an option across two lines.
1515

@@ -38,4 +38,4 @@ Note that the command line and the command-file commands are effectively combine
3838
## See also
3939

4040
[MSVC Compiler Command-Line Syntax](compiler-command-line-syntax.md)<br/>
41-
[MSVC Compiler Options](reference/compiler-options.md)
41+
[MSVC Compiler Options](compiler-options.md)

‎docs/build/reference/cl-environment-variables.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,4 +51,4 @@ This has the same effect as the following command line:
5151
## See also
5252

5353
[Setting Compiler Options](compiler-command-line-syntax.md)<br/>
54-
[MSVC Compiler Options](reference/compiler-options.md)
54+
[MSVC Compiler Options](compiler-options.md)

‎docs/build/reference/cl-invokes-the-linker.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ CL automatically invokes the linker after compiling unless the /c option is used
1616
|/Zg|Generate function prototypes|
1717
|/Zs|Check syntax|
1818

19-
For further details about linking, see [MSVC Linker Options](reference/linker-options.md).
19+
For further details about linking, see [MSVC Linker Options](linker-options.md).
2020

2121
## Example
2222

@@ -34,7 +34,7 @@ To build this program, compile with the following command line:
3434
CL MAIN.c MOD1.C MOD2.C MYGRAPH.lib
3535
```
3636

37-
CL first compiles the C source files and creates the object files MAIN.obj, MOD1.obj, and MOD2.obj. The compiler places the name of the standard library in each .obj file. For more details, see [Use Run-Time Library](reference/md-mt-ld-use-run-time-library.md).
37+
CL first compiles the C source files and creates the object files MAIN.obj, MOD1.obj, and MOD2.obj. The compiler places the name of the standard library in each .obj file. For more details, see [Use Run-Time Library](md-mt-ld-use-run-time-library.md).
3838

3939
CL passes the names of the .obj files, along with the name MYGRAPH.lib, to the linker. The linker resolves the external references as follows:
4040

@@ -46,5 +46,5 @@ CL passes the names of the .obj files, along with the name MYGRAPH.lib, to the l
4646

4747
## See also
4848

49-
[MSVC Compiler Options](reference/compiler-options.md)<br/>
49+
[MSVC Compiler Options](compiler-options.md)<br/>
5050
[Setting Compiler Options](compiler-command-line-syntax.md)

0 commit comments

Comments
 (0)