Merge pull request #3073 from mikeblome/mb-latestver

Remove old boilerplate from VS2015 topics

Author: ghogen

docs/vs-2015/code-quality/all-rules-rule-set.md

@@ -18,8 +18,6 @@ manager: "wpickett"
 # All Rules rule set
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [All Rules rule set](https://docs.microsoft.com/visualstudio/code-quality/all-rules-rule-set).  
-  
 The All Rules rule set contains all of the rules for both native and managed code. The rule set includes all the rules that are described  in the following topics:  
 
 1.  [Code Analysis for C/C++ Warnings](../code-quality/code-analysis-for-c-cpp-warnings.md)  

docs/vs-2015/code-quality/analyzing-application-quality-by-using-code-analysis-tools.md

@@ -24,8 +24,6 @@ manager: "wpickett"
 # Analyzing Application Quality by Using Code Analysis Tools
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [Analyzing Application Quality by Using Code Analysis Tools](https://docs.microsoft.com/visualstudio/code-quality/analyzing-application-quality-by-using-code-analysis-tools).  
-  
 In This Section  
  [Analyzing Managed Code Quality](../code-quality/analyzing-managed-code-quality-by-using-code-analysis.md)  
  Visual Studio code analysis for managed code provides information about managed assemblies, such as violations of the programming and design rules set forth in the Microsoft .NET Framework Design Guidelines. Warning messages identify any relevant programming and design issues and, when it is possible, supply information about how to fix the problem.  

docs/vs-2015/code-quality/analyzing-c-cpp-code-quality-by-using-code-analysis.md

@@ -26,8 +26,6 @@ manager: "ghogen"
 # Analyzing C/C++ Code Quality by Using Code Analysis
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [Analyzing C/C++ Code Quality by Using Code Analysis](https://docs.microsoft.com/visualstudio/code-quality/analyzing-c-cpp-code-quality-by-using-code-analysis).  
-  
 You can improve your C/C++ code by using the code analysis in Visual Studio to find and fix code defects.  
 
 ## In This Section  

docs/vs-2015/code-quality/analyzing-managed-code-quality-by-using-code-analysis.md

@@ -21,8 +21,6 @@ manager: "wpickett"
 # Analyzing Managed Code Quality by Using Code Analysis
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [Analyzing Managed Code Quality by Using Code Analysis](https://docs.microsoft.com/visualstudio/code-quality/analyzing-managed-code-quality-by-using-code-analysis).  
-  
 You can use the code analysis tools in Visual Studio to discover potential issues in your code, such as non-secure data access, usage violations, and design problems. Code analysis works on .NET Framework, native (C and C++), and database applications. Code analysis for managed code organizes rules in *rule sets* that target specific coding issues.  
 
 ## Common Tasks  

docs/vs-2015/code-quality/annotating-function-behavior.md

@@ -30,8 +30,6 @@ manager: "ghogen"
 # Annotating Function Behavior
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [Annotating Function Behavior](https://docs.microsoft.com/visualstudio/code-quality/annotating-function-behavior).  
-  
 In addition to annotating [function parameters and return values](../code-quality/annotating-function-parameters-and-return-values.md), you can annotate properties of the whole function.  
 
 ## Function Annotations  

docs/vs-2015/code-quality/annotating-function-parameters-and-return-values.md

@@ -135,8 +135,6 @@ manager: "ghogen"
 # Annotating Function Parameters and Return Values
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [Annotating Function Parameters and Return Values](https://docs.microsoft.com/visualstudio/code-quality/annotating-function-parameters-and-return-values).  
-  
 This article describes typical uses of annotations for simple function parameters—scalars, and pointers to structures and classes—and most kinds of buffers.  This article also shows common usage patterns for annotations. For additional annotations that are related to functions, see [Annotating Function Behavior](../code-quality/annotating-function-behavior.md)  
 
 ## Pointer Parameters  

docs/vs-2015/code-quality/annotating-locking-behavior.md

@@ -42,8 +42,6 @@ manager: "ghogen"
 # Annotating Locking Behavior
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [Annotating Locking Behavior](https://docs.microsoft.com/visualstudio/code-quality/annotating-locking-behavior).  
-  
 To avoid concurrency bugs in your multithreaded program, always follow an appropriate locking discipline and use SAL annotations.  
 
  Concurrency bugs are notoriously hard to reproduce, diagnose, and debug because they are non-deterministic. Reasoning about thread interleaving is difficult at best, and becomes impractical when you are designing a body of code that has more than a few threads. Therefore, it's good practice to follow a locking discipline in your multithreaded programs. For example, obeying a lock order while acquiring multiple locks helps avoid deadlocks, and acquiring the proper guarding lock before accessing a shared resource helps prevent race conditions.  

docs/vs-2015/code-quality/annotating-structs-and-classes.md

@@ -33,8 +33,6 @@ manager: "ghogen"
 # Annotating Structs and Classes
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [Annotating Structs and Classes](https://docs.microsoft.com/visualstudio/code-quality/annotating-structs-and-classes).  
-  
 You can annotate struct and class members by using annotations that act like invariants—they are presumed to be true at any function call or function entry/exit that involves the enclosing structure as a parameter or a result value.  
 
 ## Struct and Class Annotations  

docs/vs-2015/code-quality/anonymous-methods-and-code-analysis.md

@@ -22,8 +22,6 @@ manager: "wpickett"
 # Anonymous Methods and Code Analysis
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [Anonymous Methods and Code Analysis](https://docs.microsoft.com/visualstudio/code-quality/anonymous-methods-and-code-analysis).  
-  
 An *anonymous method* is a method that has no name. Anonymous methods are most frequently used to pass a code block as a delegate parameter.  
 
  This topic explains how Code Analysis handles warnings and metrics that are associated with anonymous methods.  

docs/vs-2015/code-quality/automatic-feature-suspension.md

@@ -19,9 +19,6 @@ manager: "wpickett"
 ---
 # Automatic feature suspension
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
-
-The latest version of this topic can be found at [Automatic feature suspension](https://docs.microsoft.com/visualstudio/code-quality/automatic-feature-suspension).
-
 If your available system memory falls to 200MB or less, Visual Studio displays the following message in the code editor.
 
  ![Alert text suspending full solution analysis](../code-quality/media/fsa-alert.png "FSA_Alert")

docs/vs-2015/code-quality/basic-correctness-rules-rule-set-for-managed-code.md

@@ -18,8 +18,6 @@ manager: "wpickett"
 # Basic Correctness Rules rule set for managed code
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [Basic Correctness Rules rule set for managed code](https://docs.microsoft.com/visualstudio/code-quality/basic-correctness-rules-rule-set-for-managed-code).  
-  
 The Basic Correctness Rules rule set focuses on logic errors and common mistakes in the usage of framework APIs. The Basic Correctness Rules include the rules in the Minimum Recommended Rules rule set. For more information, see [Managed Recommended Rules rule set for managed code](../code-quality/managed-recommended-rules-rule-set-for-managed-code.md) You should include this rule set to expand on the list of warnings that the minimum recommended rules report.  
 
  The following table describes all the rules in the Microsoft Basic Correctness Rules rule set.  

docs/vs-2015/code-quality/basic-design-guideline-rules-rule-set-for-managed-code.md

@@ -18,8 +18,6 @@ manager: "wpickett"
 # Basic Design Guideline Rules rule set for managed code
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [Basic Design Guideline Rules rule set for managed code](https://docs.microsoft.com/visualstudio/code-quality/basic-design-guideline-rules-rule-set-for-managed-code).  
-  
 You can use the Microsoft Basic Design Guideline Rules rule set to focus on making your code easier to understand and use. You should include this rule set if your project includes library code or if you want to enforce best practices for code that is easy to maintain.  
 
  The Basic Design Guideline Rules include all the rules in the Microsoft Minimum Recommeded Rules rule set. For a list of the minimum rules, see [Managed Recommended Rules rule set for managed code](../code-quality/managed-recommended-rules-rule-set-for-managed-code.md).  

docs/vs-2015/code-quality/best-practices-and-examples-sal.md

@@ -18,8 +18,6 @@ manager: "ghogen"
 # Best Practices and Examples (SAL)
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [Best Practices and Examples (SAL)](https://docs.microsoft.com/visualstudio/code-quality/best-practices-and-examples-sal).  
-  
 Here are some ways to get the most out of the Source Code Annotation Language (SAL) and avoid some common problems.  
 
 ## _In\_  

docs/vs-2015/code-quality/c1250.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C1250
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C1250](https://docs.microsoft.com/visualstudio/code-quality/c1250).  
-  
 warning C1250: Unable to load plug-in.  
 
  The Code Analysis tool reports this warning when there is an internal error in the plugin, not in the code being analyzed.

docs/vs-2015/code-quality/c1251.md

@@ -18,8 +18,6 @@ manager: "ghogen"
 # C1251
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C1251](https://docs.microsoft.com/visualstudio/code-quality/c1251).  
-  
 warning C1251: Unable to load models.  
 
  The Code Analysis tool reports this warning when there is an internal error in the model file, not in the code being analyzed.

docs/vs-2015/code-quality/c1252.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C1252
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C1252](https://docs.microsoft.com/visualstudio/code-quality/c1252).  
-  
 warning C1252: Circular or missing dependency between plugins: requires GUID  
 
  The Code Analysis tool reports this warning when there is an internal error with plugin dependencies, not in the code being analyzed.

docs/vs-2015/code-quality/c1253.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C1253
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C1253](https://docs.microsoft.com/visualstudio/code-quality/c1253).  
-  
 warning C1253: Unable to load model file.  
 
  The Code Analysis tool reports this warning when there is an internal error in the model file, not in the code being analyzed.

docs/vs-2015/code-quality/c1254.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C1254
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C1254](https://docs.microsoft.com/visualstudio/code-quality/c1254).  
-  
 warning C1254: Plugin version mismatch : version doesn't match the version of the PREfast driver  
 
  The Code Analysis tool reports this warning when there is an internal error with the plugin version, not in the code being analyzed.

docs/vs-2015/code-quality/c1255.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C1255
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C1255](https://docs.microsoft.com/visualstudio/code-quality/c1255).  
-  
 warning C1255: PCH data for plugin has incorrect length.  
 
  The Code Analysis tool reports this warning when there is an internal error in the tool, not in the code being analyzed.

docs/vs-2015/code-quality/c1256.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C1256
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C1256](https://docs.microsoft.com/visualstudio/code-quality/c1256).  
-  
 warning C1256: PCH must be both written and read.  
 
  The Code Analysis tool reports this warning when there is an internal error in the tool, not in the code being analyzed.

docs/vs-2015/code-quality/c1257.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C1257
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C1257](https://docs.microsoft.com/visualstudio/code-quality/c1257).  
-  
 warning 1257: Plugin Initialization Failure.  
 
  The Code Analysis tool reports this warning when there is an internal error in the plugin, not in the code being analyzed.

docs/vs-2015/code-quality/c26100.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C26100
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C26100](https://docs.microsoft.com/visualstudio/code-quality/c26100).  
-  
 warning C26100: Race condition. Variable \<var> should be protected by lock \<lock>.  
 
  The `_Guarded_by_` annotation in the code specifies the lock to use to guard a shared variable. Warning C26100 is generated when the guard contract is violated.  

docs/vs-2015/code-quality/c26101.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C26101
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C26101](https://docs.microsoft.com/visualstudio/code-quality/c26101).  
-  
 warning C26101: Failing to use interlocked operation properly for variable \<var>.  
 
  Windows APIs offer a variety of interlocked operations. Annotation `_Interlocked_` specifies that a variable should only be accessed through an interlocked operation. Warning C26101 is issued when an access is not consistent with the `_Interlocked_` annotation.  

docs/vs-2015/code-quality/c26105.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C26105
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C26105](https://docs.microsoft.com/visualstudio/code-quality/c26105).  
-  
 warning C26105: Lock order violation. Acquiring lock \<lock> with level \<level> causes order inversion.  
 
  Concurrency SAL supports *lock levels*. To declare a lock level, which is denoted by a string literal without double quotes, use `_Create_lock_level_`. You can impose an order of acquisition between two lock levels by using the annotation `_Set_lock_level_order_(A,B)`, which states that locks that have level `A` must be acquired before locks that have level `B`. To establish a lock order hierarchy (a partial order among lock levels), use multiple `_Set_lock_level_order_` annotations. To associate a lock with a lock level, use the `_Set_lock_level_` annotation when you declare the lock. Warning C26105 is issued when a lock ordering violation is detected.  

docs/vs-2015/code-quality/c26110.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C26110
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C26110](https://docs.microsoft.com/visualstudio/code-quality/c26110).  
-  
 warning C26110: Caller failing to hold lock \<lock> before calling function \<func>.  
 
  When a lock is required, make sure to clarify whether the function itself or its caller should acquire the lock. Warning C26110 is issued when there is a violation of the `_Requires_lock_held_` annotation.  

docs/vs-2015/code-quality/c26111.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C26111
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C26111](https://docs.microsoft.com/visualstudio/code-quality/c26111).  
-  
 warning C26111: Caller failing to release lock \<lock> before calling function \<func>.  
 
  The annotation `_Requires_lock_not_held_` imposes a precondition that the lock count for the specified lock cannot be greater than zero when the function is called. Warning C26111 is issued when a function fails to release the lock before it calls another function.  

docs/vs-2015/code-quality/c26112.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C26112
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C26112](https://docs.microsoft.com/visualstudio/code-quality/c26112).  
-  
 warning C26112: Caller cannot hold any lock before calling \<func>.  
 
  The annotation `_Requires_no_locks_held_` imposes a precondition that the caller must not hold any lock while it calls the function. Warning C26112 is issued when a function fails to release all locks before it calls another function.  

docs/vs-2015/code-quality/c26115.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C26115
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C26115](https://docs.microsoft.com/visualstudio/code-quality/c26115).  
-  
 warning C26115: Failing to release lock \<lock> in function \<func>.  
 
  Enforcement of syntactically scoped lock *acquire* and lock *release* pairs in C/C++ programs is not performed by the language. A function may introduce a locking side effect by making an observable modification to the concurrency state. For example, a lock wrapper function increments the number of lock acquisitions, or lock count, for a given lock.  

docs/vs-2015/code-quality/c26116.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C26116
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C26116](https://docs.microsoft.com/visualstudio/code-quality/c26116).  
-  
 warning C26116: Failing to acquire or to hold lock \<lock> in \<func>.  
 
  Enforcement of syntactically scoped lock *acquire* and lock *release* pairs in C/C++ programs is not performed by the language. A function may introduce a locking side effect by making an observable modification to the concurrency state. For example, a lock wrapper function increments the number of lock acquisitions, or lock count, for a given lock.You can annotate a function that has a side effect from a lock acquire or lock release by using `_Acquires_lock_` or `_Requires_lock_held`, respectively. Without such annotations, a function is expected not to change any lock count after it returns. If acquires and releases are not balanced, they are considered to be *orphaned*. Warning C26116 is issued when a function has been annotated with `_Acquires_lock_`, but it does not acquire a lock, or when a function is annotated with `_Requires_lock_held` and releases the lock.  

docs/vs-2015/code-quality/c26117.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C26117
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C26117](https://docs.microsoft.com/visualstudio/code-quality/c26117).  
-  
 warning C26117: Releasing unheld lock \<lock> in function \<func>.  
 
  Enforcement of syntactically scoped lock *acquire* and lock *release* pairs in C/C++ programs is not performed by the language. A function may introduce a locking side effect by making an observable modification to the concurrency state. For example, a lock wrapper function increments the number of lock acquisitions, or lock count, for a given lock.You can annotate a function that has a side effect from a lock acquire or lock release by using `_Acquires_lock_` or `_Releases_lock_`, respectively. Without such annotations, a function is expected not to change any lock count after it returns. If acquires and releases are not balanced, they are considered to be *orphaned*. Warning C26117 is issued when a function that has not been annotated with `_Releases_lock_` releases a lock that it doesn't hold, because the function must own the lock before it releases it.  

docs/vs-2015/code-quality/c26130.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C26130
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C26130](https://docs.microsoft.com/visualstudio/code-quality/c26130).  
-  
 warning C26130: Missing annotation _Requires_lock_held\_(\<lock>) or _No_competing_thread\_ at function \<func>. Otherwise it could be a race condition. Variable \<var> should be protected by lock \<lock>.  
 
  Warning C26130 is issued when the analyzer detects a potential race condition but infers that the function is likely to be run in a single threaded mode, for example, when the function is in the initialization stage based on certain heuristics.  

docs/vs-2015/code-quality/c26135.md

@@ -22,8 +22,6 @@ manager: "ghogen"
 # C26135
 [!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
 
-The latest version of this topic can be found at [C26135](https://docs.microsoft.com/visualstudio/code-quality/c26135).  
-  
 warning C26135: Missing annotation \<annotation> at function \<func>.  
 
  Warning C26135 is issued when the analyzer infers that a function is a lock wrapper function that has a lock acquire or lock release side effect. If the code is not intended to be a wrapper function, then either the lock is leaking (if the lock is being acquired) or it is being released incorrectly (if the lock is being released).