Skip to content

Commit 6b30ca6

Browse files
author
Colin Robertson
committed
Bulk fix of broken internal links per CATS
1 parent 004bbcd commit 6b30ca6

53 files changed

Lines changed: 109 additions & 109 deletions

File tree

Some content is hidden

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

docs/_breadcrumb/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -90,8 +90,8 @@
9090
tocHref: /cpp/data/odbc/
9191
topicHref: /cpp/data/odbc/open-database-connectivity-odbc
9292
- name: Edit, navigate and refactor code
93-
tocHref: /cpp/ide/
94-
topicHref: /cpp/ide/ide-and-tools-for-visual-cpp-development
93+
tocHref: /cpp/ide
94+
topicHref: /cpp/overview-of-cpp-development
9595
items:
9696
- name: IDE
9797
tocHref: /cpp/ide/

docs/atl/reference/ccommultithreadmodel-class.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -141,7 +141,7 @@ See [CComMultiThreadModel::AutoCriticalSection](#autocriticalsection).
141141
142142
## <a name="decrement"></a> CComMultiThreadModel::Decrement
143143
144-
This static function calls the Win32 function [InterlockedDecrement](/windows/desktop/api/winbase/nf-winbase-interlockeddecrement), which decrements the value of the variable pointed to by *p*.
144+
This static function calls the Win32 function [InterlockedDecrement](/windows/desktop/api/winnt/nf-winnt-interlockeddecrement), which decrements the value of the variable pointed to by *p*.
145145
146146
```
147147
static ULONG WINAPI Decrement(LPLONG p) throw ();
@@ -162,7 +162,7 @@ If the result of the decrement is 0, then `Decrement` returns 0. If the result o
162162
163163
## <a name="increment"></a> CComMultiThreadModel::Increment
164164
165-
This static function calls the Win32 function [InterlockedIncrement](/windows/desktop/api/winbase/nf-winbase-interlockedincrement), which increments the value of the variable pointed to by *p*.
165+
This static function calls the Win32 function [InterlockedIncrement](/windows/desktop/api/winnt/nf-winnt-interlockedincrement), which increments the value of the variable pointed to by *p*.
166166
167167
```
168168
static ULONG WINAPI Increment(LPLONG p) throw ();

docs/atl/reference/ccommultithreadmodelnocs-class.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ See [CComMultiThreadModel::AutoCriticalSection](../../atl/reference/ccommultithr
101101

102102
## <a name="decrement"></a> CComMultiThreadModelNoCS::Decrement
103103

104-
This static function calls the Win32 function [InterlockedDecrement](/windows/desktop/api/winbase/nf-winbase-interlockeddecrement), which decrements the value of the variable pointed to by *p*.
104+
This static function calls the Win32 function [InterlockedDecrement](/windows/desktop/api/winnt/nf-winnt-interlockeddecrement), which decrements the value of the variable pointed to by *p*.
105105

106106
```
107107
static ULONG WINAPI Decrement(LPLONG p) throw();
@@ -122,7 +122,7 @@ If the result of the decrement is 0, then `Decrement` returns 0. If the result o
122122

123123
## <a name="increment"></a> CComMultiThreadModelNoCS::Increment
124124

125-
This static function calls the Win32 function [InterlockedIncrement](/windows/desktop/api/winbase/nf-winbase-interlockedincrement), which increments the value of the variable pointed to by *p*.
125+
This static function calls the Win32 function [InterlockedIncrement](/windows/desktop/api/winnt/nf-winnt-interlockedincrement), which increments the value of the variable pointed to by *p*.
126126

127127
```
128128
static ULONG WINAPI Increment(LPLONG p) throw();

docs/build/customize-cmake-settings.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -46,19 +46,19 @@ You can also directly edit `CMakeSettings.json` to create custom configurations
4646

4747
- **generator**: maps to the CMake **-G** switch and specifies the generator to be used. This property can also be used as a macro, `${generator}`, when composing other property values. Visual Studio currently supports the following CMake generators:
4848

49-
- "Ninja"
50-
- "Visual Studio 14 2015"
51-
- "Visual Studio 14 2015 ARM"
52-
- "Visual Studio 14 2015 Win64"
53-
- "Visual Studio 15 2017"
54-
- "Visual Studio 15 2017 ARM"
55-
- "Visual Studio 15 2017 Win64"
49+
- "Ninja"
50+
- "Visual Studio 14 2015"
51+
- "Visual Studio 14 2015 ARM"
52+
- "Visual Studio 14 2015 Win64"
53+
- "Visual Studio 15 2017"
54+
- "Visual Studio 15 2017 ARM"
55+
- "Visual Studio 15 2017 Win64"
5656

57-
Because Ninja is designed for fast build speeds instead of flexibility and function, it is set as the default. However, some CMake projects may be unable to correctly build using Ninja. If this occurs, you can instruct CMake to generate a Visual Studio project instead.
57+
Because Ninja is designed for fast build speeds instead of flexibility and function, it is set as the default. However, some CMake projects may be unable to correctly build using Ninja. If this occurs, you can instruct CMake to generate a Visual Studio project instead.
5858

59-
To specify a Visual Studio generator, open the `CMakeSettings.json` from the main menu by choosing **CMake | Change CMake Settings**. Delete “Ninja” and type “V”. This activates IntelliSense, which enables you to choose the generator you want.
59+
To specify a Visual Studio generator, open the `CMakeSettings.json` from the main menu by choosing **CMake | Change CMake Settings**. Delete “Ninja” and type “V”. This activates IntelliSense, which enables you to choose the generator you want.
6060

61-
When the active configuration specifies a Visual Studio generator, by default MSBuild.exe is invoked with `-m -v:minimal` arguments. To customize the build, inside the `CMakeSettings.json` file, you can specify additional [MSBuild command line arguments](../build/msbuild-visual-cpp-overview.md) to be passed to the build system via the `buildCommandArgs` property:
61+
When the active configuration specifies a Visual Studio generator, by default MSBuild.exe is invoked with `-m -v:minimal` arguments. To customize the build, inside the `CMakeSettings.json` file, you can specify additional [MSBuild command line arguments](../build/reference/msbuild-visual-cpp-overview.md) to be passed to the build system via the `buildCommandArgs` property:
6262

6363
```json
6464
"buildCommandArgs": "-m:8 -v:minimal -p:PreferredToolArchitecture=x64"

docs/build/reference/file-types-created-for-visual-cpp-projects.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.assetid: 2b0ee2e0-ae81-4185-9bb9-11da3c99a283
88

99
This topic describes all the types of files that are associated with Visual Studio projects for classic desktop applications. The actual files included in your project depend on the project type and the options you select when using a wizard.
1010

11-
- [Project and Solution Files]()
11+
- [Project and Solution Files](project-and-solution-files.md)
1212

1313
- [CLR Projects](files-created-for-clr-projects.md)
1414

@@ -61,8 +61,8 @@ The following table shows common files in a Visual Studio project, and identifie
6161
|.vap|Project|A Visual Studio Analyzer project file.|
6262
|.vbg|Solution|A compatible project group file.|
6363
|.vbp, .vip, .vbproj|Project|The Visual Basic project file.|
64-
|.vcxitems|Project|Shared Items project for sharing code files between multiple C++ projects. See [Project Files and Makefiles]() for more information.|
65-
|.vcxproj|Project|The Visual Studio project file. See [Project Files and Makefiles]() for more information.|
64+
|.vcxitems|Project|Shared Items project for sharing code files between multiple C++ projects. See [Project and Solution Files](project-and-solution-files.md) for more information.|
65+
|.vcxproj|Project|The Visual Studio project file. See [Project and Solution Files](project-and-solution-files.md) for more information.|
6666
|.vcxproj.filters|Project|When Solution Explorer is used to add a file to a project, the filters file defines where in the Solution Explorer tree view the file is added, based on its file name extension.|
6767
|.vdproj|Project|The Visual Studio deployment project file.|
6868
|.vmx|Project|The macro project file.|

docs/cpp/constexpr-cpp.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ constexpr float exp(float x, int n)
9393
9494
## extern constexpr
9595

96-
The [/Zc:externConstexpr](../build/reference/zc-externconstexpr.md) compiler option causes the compiler to apply [external linkage]() to variables declared by using **extern constexpr**. In earlier versions of Visual Studio, and by default or if **/Zc:externConstexpr-** is specified, Visual Studio applies internal linkage to **constexpr** variables even if the **extern** keyword is used. The **/Zc:externConstexpr** option is available starting in Visual Studio 2017 Update 15.6. and is off by default. The /permissive- option does not enable /Zc:externConstexpr.
96+
The [/Zc:externConstexpr](../build/reference/zc-externconstexpr.md) compiler option causes the compiler to apply [external linkage](../c-language/external-linkage.md) to variables declared by using **extern constexpr**. In earlier versions of Visual Studio, and by default or if **/Zc:externConstexpr-** is specified, Visual Studio applies internal linkage to **constexpr** variables even if the **extern** keyword is used. The **/Zc:externConstexpr** option is available starting in Visual Studio 2017 Update 15.6. and is off by default. The /permissive- option does not enable /Zc:externConstexpr.
9797

9898
## Example
9999

docs/cpp/storage-classes-cpp.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -156,7 +156,7 @@ Objects and variables declared as **extern** declare an object that is defined i
156156

157157
Declaration of **const** variables with the **extern** storage class forces the variable to have external linkage. An initialization of an **extern const** variable is allowed in the defining translation unit. Initializations in translation units other than the defining translation unit produce undefined results. For more information, see [Using extern to Specify Linkage](../cpp/using-extern-to-specify-linkage.md)
158158

159-
The [/Zc:externConstexpr](../build/reference/zc-externconstexpr.md) compiler option causes the compiler to apply [external linkage]() to variables declared by using `extern constexpr`. In earlier versions of Visual Studio, and by default or if **/Zc:externConstexpr-** is specified, Visual Studio applies internal linkage to **constexpr** variables even if the **extern** keyword is used. The **/Zc:externConstexpr** option is available starting in Visual Studio 2017 Update 15.6. and is off by default. The /permissive- option does not enable /Zc:externConstexpr.
159+
The [/Zc:externConstexpr](../build/reference/zc-externconstexpr.md) compiler option causes the compiler to apply [external linkage](../c-language/external-linkage.md) to variables declared by using `extern constexpr`. In earlier versions of Visual Studio, and by default or if **/Zc:externConstexpr-** is specified, Visual Studio applies internal linkage to **constexpr** variables even if the **extern** keyword is used. The **/Zc:externConstexpr** option is available starting in Visual Studio 2017 Update 15.6. and is off by default. The /permissive- option does not enable /Zc:externConstexpr.
160160

161161
The following code shows two **extern** declarations, `DefinedElsewhere` (which refers to a name defined in a different translation unit) and `DefinedHere` (which refers to a name defined in an enclosing scope):
162162

docs/cppcx/visual-c-language-reference-c-cx.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ By using C++/CX, you can create:
1818

1919
- C++ Windows Runtime components that can be consumed by JavaScript-based Windows apps. For more information, see [Creating Windows Runtime Components in C++](/windows/uwp/winrt-components/creating-windows-runtime-components-in-cpp).
2020

21-
- Windows DirectX games and graphics-intensive apps. For more information, see [Create a simple UWP Game with DirectX](/windows/uwp/gaming/tutorial--create-your-first-metro-style-directx-game).
21+
- Windows DirectX games and graphics-intensive apps. For more information, see [Create a simple UWP Game with DirectX](/windows/uwp/gaming/tutorial--create-your-first-uwp-directx-game).
2222

2323
## Related articles
2424

docs/data/data-access-in-cpp.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.assetid: 95da6237-bbe2-480a-ae50-3a520051ceff
88

99
Virtually all database products, SQL and NoSQL, provide an interface for native C++ applications. The industry standard interface is ODBC which is supported by all major SQL database products and many NoSQL products. For non-Microsoft products, consult the vendor for more information. Third-party libraries with various license terms are also available.
1010

11-
Since 2011 Microsoft has aligned on ODBC as the standard for native applications to connecting to Microsoft SQL Server databases, both on-premises and in the cloud. For more information, see [Data Access Programming \(MFC-ATL\)](data-access-programming-mfc-atl.md). C++/CLI libraries can use either the native ODBC drivers or ADO.NET. For more information, see [Data Access Using ADO.NET (C++/CLI)](/dotnet/data-access-using-adonet-cpp-cli.md) and [Accessing data in Visual Studio](https://docs.microsoft.com/visualstudio/data-tools/accessing-data-in-visual-studio).
11+
Since 2011 Microsoft has aligned on ODBC as the standard for native applications to connecting to Microsoft SQL Server databases, both on-premises and in the cloud. For more information, see [Data Access Programming \(MFC-ATL\)](data-access-programming-mfc-atl.md). C++/CLI libraries can use either the native ODBC drivers or ADO.NET. For more information, see [Data Access Using ADO.NET (C++/CLI)](../dotnet/data-access-using-adonet-cpp-cli.md) and [Accessing data in Visual Studio](https://docs.microsoft.com/visualstudio/data-tools/accessing-data-in-visual-studio).
1212

1313
## In This Section
1414

docs/data/oledb/crowset-class.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ An accessor class. The default is `CAccessorBase`.
3535
|[Close](#close)|Releases rows and the current `IRowset` interface.|
3636
|[Compare](#compare)|Compares two bookmarks using [IRowsetLocate::Compare](/previous-versions/windows/desktop/ms709539(v=vs.85)).|
3737
|[CRowset](#crowset)|Creates a new `CRowset` object and (optionally) associates it with an `IRowset` interface supplied as a parameter.|
38-
|[Delete](#delete)|Deletes rows from the rowset using [IRowsetChange:DeleteRows](/previous-versions/windows/desktop/ms724362(v=vs.85)(v%3dvs.85)).|
38+
|[Delete](#delete)|Deletes rows from the rowset using [IRowsetChange:DeleteRows](/previous-versions/windows/desktop/ms724362(v=vs.85)).|
3939
|[FindNextRow](#findnextrow)|Finds the next matching row after the specified bookmark.|
4040
|[GetApproximatePosition](#getapproximateposition)|Returns the approximate position of a row corresponding to a bookmark.|
4141
|[GetData](#getdata)|Retrieves data from the rowset's copy of the row.|
@@ -146,7 +146,7 @@ CRowset(IRowset* pRowset);
146146

147147
## <a name="delete"></a> CRowset::Delete
148148

149-
Calls [IRowsetChange::DeleteRows](/previous-versions/windows/desktop/ms724362(v=vs.85)(v%3dvs.85)) to delete the current row from the rowset.
149+
Calls [IRowsetChange::DeleteRows](/previous-versions/windows/desktop/ms724362(v=vs.85)) to delete the current row from the rowset.
150150

151151
### Syntax
152152

0 commit comments

Comments
 (0)