fixed broken links and added redirect

mikeblome · mikeblome · commit a2b000c0210b · 2019-11-19T10:17:52.000-08:00
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -730,6 +730,11 @@
          "redirect_url": "/cpp/cpp/cpp-language-reference",
          "redirect_document_id": false
       },
+      {
+         "source_path": "docs/cpp/cpp-exception-handling.md",
+         "redirect_url": "/cpp/cpp/exception-handling-in-visual-cpp.md",
+         "redirect_document_id": false
+      },
       {
          "source_path": "docs/cpp/types-of-linkage.md",
          "redirect_url": "/cpp/cpp/program-and-linkage-cpp",
diff --git a/docs/build/reference/gx-enable-exception-handling.md b/docs/build/reference/gx-enable-exception-handling.md
@@ -1,6 +1,6 @@
 ---
 title: "/GX (Enable Exception Handling)"
-ms.date: "11/04/2016"
+ms.date: "11/19/2019"
 f1_keywords: ["/gx"]
 helpviewer_keywords: ["exception handling, enabling", "/GX compiler option [C++]", "-GX compiler option [C++]", "cl.exe compiler, exception handling", "enable exception handling compiler option [C++]", "GX compiler option [C++]"]
 ms.assetid: 933b43ba-de77-4ff8-a48b-7074de90bc1c
@@ -21,8 +21,6 @@ Deprecated. Enables synchronous exception handling using the assumption that fun
 
 By default, **/EHsc**, the equivalent of **/GX**, is in effect when you compile by using the Visual Studio development environment. When using the command line tools, no exception handling is specified. This is the equivalent of **/GX-**.
 
-For more information, see [C++ Exception Handling](../../cpp/cpp-exception-handling.md).
-
 ### To set this compiler option in the Visual Studio development environment
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
diff --git a/docs/cpp/bad-cast-exception.md b/docs/cpp/bad-cast-exception.md
@@ -115,4 +115,4 @@ const char* what() const noexcept override;
 
 [dynamic_cast Operator](../cpp/dynamic-cast-operator.md)\
 [Keywords](../cpp/keywords-cpp.md)\
-[C++ Exception Handling](../cpp/cpp-exception-handling.md)
+[Modern C++ best practices for exceptions and error handling](../cpp/errors-and-exception-handling-modern-cpp.md)
diff --git a/docs/cpp/exception-handling-in-visual-cpp.md b/docs/cpp/exception-handling-in-visual-cpp.md
@@ -12,7 +12,7 @@ An exception is an error condition, possibly outside the program's control, that
 
 The Microsoft C++ compiler (MSVC) supports three kinds of exception handling:
 
-- [C++ exception handling](cpp-exception-handling.md)
+- [C++ exception handling](errors-and-exception-handling-modern-cpp.md)
 
    For most C++ programs, you should use C++ exception handling, which is type-safe and ensures that object destructors are invoked during stack unwinding.
 
diff --git a/docs/cpp/exception-specifications-throw-cpp.md b/docs/cpp/exception-specifications-throw-cpp.md
@@ -119,4 +119,4 @@ in handler
 ## See also
 
 [try, throw, and catch Statements (C++)](../cpp/try-throw-and-catch-statements-cpp.md)<br/>
-[C++ Exception Handling](../cpp/cpp-exception-handling.md)
+[Modern C++ best practices for exceptions and error handling](errors-and-exception-handling-modern-cpp.md)
diff --git a/docs/cpp/how-catch-blocks-are-evaluated-cpp.md b/docs/cpp/how-catch-blocks-are-evaluated-cpp.md
@@ -55,4 +55,4 @@ In this example, the ellipsis **catch** handler is the only handler that is exam
 
 ## See also
 
-[C++ Exception Handling](../cpp/cpp-exception-handling.md)
+[Modern C++ best practices for exceptions and error handling](../cpp/errors-and-exception-handling-modern-cpp.md)
diff --git a/docs/cpp/mixing-c-structured-and-cpp-exceptions.md b/docs/cpp/mixing-c-structured-and-cpp-exceptions.md
@@ -32,4 +32,4 @@ If you mix structured and C++ exceptions, be aware of these potential issues:
 
 ## See also
 
-[C++ Exception Handling](../cpp/cpp-exception-handling.md)
+[Modern C++ best practices for exceptions and error handling](../cpp/errors-and-exception-handling-modern-cpp.md)
diff --git a/docs/cpp/noexcept-cpp.md b/docs/cpp/noexcept-cpp.md
@@ -1,6 +1,6 @@
 ---
 title: "noexcept (C++)"
-ms.date: "01/12/2018"
+ms.date: "11/19/2019"
 f1_keywords: ["noexcept_cpp"]
 ms.assetid: df24edb9-c6a6-4e37-9914-fd5c0c3716a8
 ---
@@ -41,5 +41,5 @@ T copy_object(const T& obj) noexcept(std::is_pod<T>)
 
 ## See also
 
-[C++ Exception Handling](cpp-exception-handling.md)<br/>
+[Modern C++ best practices for exceptions and error handling](errors-and-exception-handling-modern-cpp.md)<br/>
 [Exception Specifications (throw, noexcept)](exception-specifications-throw-cpp.md)
diff --git a/docs/cpp/try-throw-and-catch-statements-cpp.md b/docs/cpp/try-throw-and-catch-statements-cpp.md
@@ -72,7 +72,7 @@ catch(...) {
 
 ## See also
 
-[C++ Exception Handling](../cpp/cpp-exception-handling.md)<br/>
+[Modern C++ best practices for exceptions and error handling](../cpp/errors-and-exception-handling-modern-cpp.md)<br/>
 [Keywords](../cpp/keywords-cpp.md)<br/>
 [Unhandled C++ Exceptions](../cpp/unhandled-cpp-exceptions.md)<br/>
 [__uncaught_exception](../c-runtime-library/reference/uncaught-exception.md)
diff --git a/docs/cpp/unhandled-cpp-exceptions.md b/docs/cpp/unhandled-cpp-exceptions.md
@@ -45,4 +45,4 @@ The `term_func` function should terminate the program or current thread, ideally
 
 ## See also
 
-[C++ Exception Handling](../cpp/cpp-exception-handling.md)
+[Modern C++ best practices for exceptions and error handling](../cpp/errors-and-exception-handling-modern-cpp.md)
diff --git a/docs/dotnet/how-to-catch-exceptions-in-native-code-thrown-from-msil.md b/docs/dotnet/how-to-catch-exceptions-in-native-code-thrown-from-msil.md
@@ -8,7 +8,7 @@ ms.assetid: c15afd2b-8505-43bf-8a4a-f1d41532a124
 
 In native code, you can catch native C++ exception from MSIL.  You can catch CLR exceptions with `__try` and `__except`.
 
-For more information, see [Structured Exception Handling (C/C++)](../cpp/structured-exception-handling-c-cpp.md) and [C++ Exception Handling](../cpp/cpp-exception-handling.md).
+For more information, see [Structured Exception Handling (C/C++)](../cpp/structured-exception-handling-c-cpp.md) and [Modern C++ best practices for exceptions and error handling](../cpp/errors-and-exception-handling-modern-cpp.md).
 
 ## Example
 
diff --git a/docs/mfc/exception-handling-in-mfc.md b/docs/mfc/exception-handling-in-mfc.md
@@ -94,5 +94,5 @@ The following articles compare the MFC exception macros with the C++ exception k
 
 ## See also
 
-[C++ Exception Handling](../cpp/cpp-exception-handling.md)<br/>
+[Modern C++ best practices for exceptions and error handling](../cpp/errors-and-exception-handling-modern-cpp.md)<br/>
 [How Do I: Create my Own Custom Exception Classes](https://go.microsoft.com/fwlink/p/?linkid=128045)
diff --git a/docs/mfc/exceptions-catching-and-deleting-exceptions.md b/docs/mfc/exceptions-catching-and-deleting-exceptions.md
@@ -6,7 +6,7 @@ ms.assetid: 7c233ff0-89de-4de0-a68a-9e9cdb164311
 ---
 # Exceptions: Catching and Deleting Exceptions
 
-The following instructions and examples show you how to catch and delete exceptions. For more information on the **try**, **catch**, and **throw** keywords, see [C++ Exception Handling](../cpp/cpp-exception-handling.md).
+The following instructions and examples show you how to catch and delete exceptions. For more information on the **try**, **catch**, and **throw** keywords, see [Modern C++ best practices for exceptions and error handling](../cpp/errors-and-exception-handling-modern-cpp.md).
 
 Your exception handlers must delete exception objects they handle, because failure to delete the exception causes a memory leak whenever that code catches an exception.
 
diff --git a/docs/mfc/exceptions-ole-exceptions.md b/docs/mfc/exceptions-ole-exceptions.md
@@ -6,7 +6,7 @@ ms.assetid: 2f8e0161-b94f-48bb-a5a2-6f644b192527
 ---
 # Exceptions: OLE Exceptions
 
-The techniques and facilities for handling exceptions in OLE are the same as those for handling other exceptions. For further information on exception handling, see the article [C++ Exception Handling](../cpp/cpp-exception-handling.md).
+The techniques and facilities for handling exceptions in OLE are the same as those for handling other exceptions. For further information on exception handling, see the article [Modern C++ best practices for exceptions and error handling](../cpp/errors-and-exception-handling-modern-cpp.md).
 
 All exception objects are derived from the abstract base class `CException`. MFC provides two classes for handling OLE exceptions:
 

Original file line number	Diff line number	Diff line change
`@@ -55,4 +55,4 @@ In this example, the ellipsis catch handler is the only handler that is exam`
`55`	`55`
`56`	`56`	`## See also`
`57`	`57`
`58`		`-[C++ Exception Handling](../cpp/cpp-exception-handling.md)`
	`58`	`+[Modern C++ best practices for exceptions and error handling](../cpp/errors-and-exception-handling-modern-cpp.md)`
Original file line number	Diff line number	Diff line change
`@@ -32,4 +32,4 @@ If you mix structured and C++ exceptions, be aware of these potential issues:`
`32`	`32`
`33`	`33`	`## See also`
`34`	`34`
`35`		`-[C++ Exception Handling](../cpp/cpp-exception-handling.md)`
	`35`	`+[Modern C++ best practices for exceptions and error handling](../cpp/errors-and-exception-handling-modern-cpp.md)`
Original file line number	Diff line number	Diff line change
@@ -45,4 +45,4 @@ The `term_func` function should terminate the program or current thread, ideally
`45`	`45`
`46`	`46`	`## See also`
`47`	`47`
`48`		`-[C++ Exception Handling](../cpp/cpp-exception-handling.md)`
	`48`	`+[Modern C++ best practices for exceptions and error handling](../cpp/errors-and-exception-handling-modern-cpp.md)`