Bulk fix of broken internal links per CATS

Author: Colin Robertson

docs/_breadcrumb/toc.yml

@@ -90,8 +90,8 @@
           tocHref: /cpp/data/odbc/
           topicHref: /cpp/data/odbc/open-database-connectivity-odbc
       - name: Edit, navigate and refactor code
-        tocHref: /cpp/ide/
-        topicHref: /cpp/ide/ide-and-tools-for-visual-cpp-development
+        tocHref: /cpp/ide
+        topicHref: /cpp/overview-of-cpp-development
         items:
         - name: IDE
           tocHref: /cpp/ide/

docs/atl/reference/ccommultithreadmodel-class.md

@@ -141,7 +141,7 @@ See [CComMultiThreadModel::AutoCriticalSection](#autocriticalsection).
 
 ##  <a name="decrement"></a>  CComMultiThreadModel::Decrement
 
-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*.
+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*.
 
 ```
 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
 
 ##  <a name="increment"></a>  CComMultiThreadModel::Increment
 
-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*.
+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*.
 
 ```
 static ULONG WINAPI Increment(LPLONG p) throw ();

docs/atl/reference/ccommultithreadmodelnocs-class.md

@@ -101,7 +101,7 @@ See [CComMultiThreadModel::AutoCriticalSection](../../atl/reference/ccommultithr
 
 ##  <a name="decrement"></a>  CComMultiThreadModelNoCS::Decrement
 
-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*.
+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*.
 
 ```
 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
 
 ##  <a name="increment"></a>  CComMultiThreadModelNoCS::Increment
 
-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*.
+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*.
 
 ```
 static ULONG WINAPI Increment(LPLONG p) throw();

docs/build/customize-cmake-settings.md

@@ -46,19 +46,19 @@ You can also directly edit  `CMakeSettings.json` to create custom configurations
 
 - **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:
 
-    - "Ninja"
-    - "Visual Studio 14 2015"
-    - "Visual Studio 14 2015 ARM"
-    - "Visual Studio 14 2015 Win64"
-    - "Visual Studio 15 2017"
-    - "Visual Studio 15 2017 ARM"
-    - "Visual Studio 15 2017 Win64"
+  - "Ninja"
+  - "Visual Studio 14 2015"
+  - "Visual Studio 14 2015 ARM"
+  - "Visual Studio 14 2015 Win64"
+  - "Visual Studio 15 2017"
+  - "Visual Studio 15 2017 ARM"
+  - "Visual Studio 15 2017 Win64"
 
-    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.
+  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.
 
-    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.
+  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.
 
-    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:
+  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:
 
     ```json
     "buildCommandArgs": "-m:8 -v:minimal -p:PreferredToolArchitecture=x64"

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

@@ -8,7 +8,7 @@ ms.assetid: 2b0ee2e0-ae81-4185-9bb9-11da3c99a283
 
 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.
 
-- [Project and Solution Files]()
+- [Project and Solution Files](project-and-solution-files.md)
 
 - [CLR Projects](files-created-for-clr-projects.md)
 
@@ -61,8 +61,8 @@ The following table shows common files in a Visual Studio project, and identifie
 |.vap|Project|A Visual Studio Analyzer project file.|
 |.vbg|Solution|A compatible project group file.|
 |.vbp, .vip, .vbproj|Project|The Visual Basic project file.|
-|.vcxitems|Project|Shared Items project for sharing code files between multiple C++ projects. See [Project Files and Makefiles]() for more information.|
-|.vcxproj|Project|The Visual Studio project file. See [Project Files and Makefiles]() for more information.|
+|.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.|
+|.vcxproj|Project|The Visual Studio project file. See [Project and Solution Files](project-and-solution-files.md) for more information.|
 |.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.|
 |.vdproj|Project|The Visual Studio deployment project file.|
 |.vmx|Project|The macro project file.|

docs/cpp/constexpr-cpp.md

@@ -93,7 +93,7 @@ constexpr float exp(float x, int n)
 
 ## extern constexpr
 
-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.
+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.
 
 ## Example
 

docs/cpp/storage-classes-cpp.md

@@ -156,7 +156,7 @@ Objects and variables declared as **extern** declare an object that is defined i
 
 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)
 
-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.
+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.
 
 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):
 

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

@@ -18,7 +18,7 @@ By using C++/CX, you can create:
 
 - 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).
 
-- 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).
+- 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).
 
 ## Related articles
 

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

@@ -8,7 +8,7 @@ ms.assetid: 95da6237-bbe2-480a-ae50-3a520051ceff
 
 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.
 
-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).
+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).
 
 ## In This Section
 

docs/data/oledb/crowset-class.md

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

docs/data/oledb/irowsetchangeimpl-class.md

@@ -90,7 +90,7 @@ STDMETHOD (DeleteRows )(HCHAPTER /* hReserved */,
 
 #### Parameters
 
-See [IRowsetChange::DeleteRows](/previous-versions/windows/desktop/ms724362(v=vs.85)(v%3dvs.85)) in the *OLE DB Programmer's Reference*.
+See [IRowsetChange::DeleteRows](/previous-versions/windows/desktop/ms724362(v=vs.85)) in the *OLE DB Programmer's Reference*.
 
 ## <a name="insertrow"></a> IRowsetChangeImpl::InsertRow
 

docs/data/oledb/obtaining-metadata-with-schema-rowsets.md

@@ -43,7 +43,7 @@ CRestrictions<CAccessor<CColumnsInfo>
 
 The [CRestrictions](../../data/oledb/crestrictions-class.md) class supplies the restriction support. After you create an instance of the schema rowset, call [CRestrictions::Open](../../data/oledb/crestrictions-open.md). This method returns a result set based on the restrictions that you specify.
 
-To specify restrictions, refer to [Appendix B: Schema Rowsets](/previous-versions/windows/desktop/ms712921(v=vs.85)) and look up the rowset that you're using. For example, `CColumns` corresponds to the [COLUMNS Rowset](/previous-versions/windows/desktop/ms723052(v=vs.85)\(v%3dvs.85\)); that topic lists the restriction columns in the COLUMNS rowset: TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_NAME. You must follow that order in specifying your restrictions.
+To specify restrictions, refer to [Appendix B: Schema Rowsets](/previous-versions/windows/desktop/ms712921(v=vs.85)) and look up the rowset that you're using. For example, `CColumns` corresponds to the [COLUMNS Rowset](/previous-versions/windows/desktop/ms723052(v=vs.85)); that topic lists the restriction columns in the COLUMNS rowset: TABLE_CATALOG, TABLE_SCHEMA, TABLE_NAME, COLUMN_NAME. You must follow that order in specifying your restrictions.
 
 So, for example, if you want to restrict by table name, TABLE_NAME is the third restriction column, and then call `Open`, specifying the wanted table name as the third restriction parameter, as shown in the following example.
 

docs/data/oledb/ole-db-consumer-templates-cpp.md

@@ -14,7 +14,7 @@ The OLE DB Consumer Templates support the OLE DB version 2.6 specification. (The
 
 - Native C/C++ data types for OLE DB programming.
 
-To use the OLE DB Templates, you should be familiar with C++ templates, COM, and the OLE DB interfaces. If you aren't familiar with OLE DB, see [OLE DB Programmer's Reference](/previous-versions/windows/desktop/ms718124(v=vs.85)).
+To use the OLE DB Templates, you should be familiar with C++ templates, COM, and the OLE DB interfaces. If you aren't familiar with OLE DB, see [Microsoft OLE DB Driver for SQL Server](/sql/connect/oledb/oledb-driver-for-sql-server).
 
 The OLE DB Templates support the existing OLE DB object model rather than adding a new object model. The top-layer classes in the OLE DB Consumer Templates parallel the components defined in the OLE DB specification. The design of the OLE DB Consumer Templates includes advanced features such as multiple accessors on a rowset. The use of templates and multiple inheritance makes the library small and flexible.
 
@@ -51,4 +51,4 @@ For more information, see the following topics:
 [OLE DB Programming](../../data/oledb/ole-db-programming.md)<br/>
 [Data Access](../data-access-in-cpp.md)<br/>
 [OLE DB SDK Documentation](/previous-versions/windows/desktop/ms722784(v=vs.85))<br/>
-[OLE DB Programmer's Reference](/sql/connect/oledb/ole-db/oledb-driver-for-sql-server-programming)
+[Microsoft OLE DB Driver for SQL Server](/sql/connect/oledb/oledb-driver-for-sql-server)

docs/data/oledb/ole-db-programming.md

@@ -20,7 +20,7 @@ Also, you can use attributes to implement the OLE DB consumer templates.
 |Using the OLE DB provider templates (conceptual topics)|[OLE DB Provider Templates](../../data/oledb/ole-db-provider-templates-cpp.md)|
 |OLE DB templates classes and macros|[OLE DB Templates Reference](../../data/oledb/ole-db-templates.md) (Visual C++)|
 |OLE DB consumer attributes|[OLE DB Consumer Attributes](../../windows/ole-db-consumer-attributes.md)|
-|OLE DB interfaces|[OLE DB programmer's reference](/sql/connect/oledb/ole-db/oledb-driver-for-sql-server-programming(v%3dvs.85)) (in the Windows SDK)|
+|OLE DB interfaces|[OLE DB programmer's reference](/sql/connect/oledb/oledb-driver-for-sql-server) (in the Windows SDK)|
 |OLE DB templates samples|[OLE DB Templates Samples](https://github.com/Microsoft/VCSamples)|
 |Data access programming overview (Visual C++)|[Data Access Programming](../../data/data-access-programming-mfc-atl.md)|
 |ODBC conceptual topics|[Open Database Connectivity (ODBC)](../../data/odbc/open-database-connectivity-odbc.md)|

docs/dotnet/converting-projects-from-mixed-mode-to-pure-intermediate-language.md

@@ -70,16 +70,16 @@ If you are using an earlier version of the Visual C++ compiler toolset that supp
    |[Boolean](/dotnet/api/system.boolean)|Represents a Boolean value.|
    |[Byte](/dotnet/api/system.byte)|Represents an 8-bit unsigned integer.|
    |[Char](/dotnet/api/system.char)|Represents a Unicode character.|
-   |[DateTime](/dotnet/api/system.datetime.datetime.aspx)|Represents an instant in time, typically expressed as a date and time of day.|
+   |[DateTime](/dotnet/api/system.datetime)|Represents an instant in time, typically expressed as a date and time of day.|
    |[Decimal](/dotnet/api/system.decimal)|Represents a decimal number.|
    |[Double](/dotnet/api/system.double)|Represents a double-precision floating-point number.|
    |[Guid](/dotnet/api/system.guid)|Represents a globally unique identifier (GUID).|
    |[Int16](/dotnet/api/system.int16)|Represents a 16-bit signed integer.|
    |[Int32](/dotnet/api/system.int32)|Represents a 32-bit signed integer.|
    |[Int64](/dotnet/api/system.int64)|Represents a 64-bit signed integer.|
    |[IntPtr](/dotnet/api/system.intptr)|A platform-specific type that is used to represent a pointer or a handle.|
-   |[SByte](/dotnet/api/system.byte.aspx)|Represents an 8-bit signed integer.|
-   |[Single](/dotnet/api/system.single.aspx)|Represents a single-precision floating-point number.|
+   |[SByte](/dotnet/api/system.byte)|Represents an 8-bit signed integer.|
+   |[Single](/dotnet/api/system.single)|Represents a single-precision floating-point number.|
    |[TimeSpan](/dotnet/api/system.timespan)|Represents a time interval.|
    |[UInt16](/dotnet/api/system.uint16)|Represents a 16-bit unsigned integer.|
    |[UInt32](/dotnet/api/system.uint32)|Represents a 32-bit unsigned integer.|