Merge pull request #6482 from v-thepet/links4-29

BrokenLinkBugs: Fix broken links OPS 4/26/20

Author: GitHubber17

docs/python/publish-to-app-service-windows.md

@@ -58,7 +58,7 @@ With an active Azure subscription, create an App Service with an empty Web App a
 
 Create a temporary App Service without needing an Azure subscription as follows:
 
-1. Open your browser to [try.azurewebsites.net](https://try.azurewebsites.net).
+1. Open your browser to [https://azure.microsoft.com/try/app-service/web/](https://azure.microsoft.com/try/app-service/web/).
 1. Select **Web App** for the app type, then select **Next**.
 1. Select **Empty Site**, followed by **Create**.
 1. Sign in with a social login of your choice, and after a short time your site is ready at the displayed URL.

docs/sharepoint/create-sharepoint-solutions.md

@@ -16,7 +16,7 @@ ms.workload:
 # Create SharePoint solutions
   You can create SharePoint applications in Visual Studio as an alternative to creating them in SharePoint Designer. Visual Studio promotes rapid SharePoint development by providing such features as advanced debugging tools, IntelliSense, statement completion, and project templates. Visual Studio also takes advantage of advanced .NET Framework-based tools and languages. You can develop SharePoint projects by using either Visual Basic or Visual C#, and you can develop app for SharePoint projects by using JavaScript.
 
- For information about SharePoint 2013 and SharePoint add-ins, see [SharePoint 2013](https://products.office.com/previous-versions/microsoft-sharepoint-2013) and [Build apps for SharePoint](/sharepoint/dev/sp-add-ins/sharepoint-add-ins).
+ For information about SharePoint 2013 and SharePoint add-ins, see [SharePoint 2013](https://www.microsoft.com/microsoft-365/previous-versions/microsoft-sharepoint-2013) and [Build apps for SharePoint](/sharepoint/dev/sp-add-ins/sharepoint-add-ins).
 
 > [!NOTE]
 > Find out how to use the new [SharePoint add-in model](/sharepoint/dev/sp-add-ins/sharepoint-add-ins) to extend the SharePoint experience for your users. These add-ins have very small footprints compared to SharePoint solutions, and you can build them by using almost any web programming technology such as HTML5, JavaScript, CSS3, and XML.

docs/sharepoint/developing-sharepoint-solutions.md

@@ -19,7 +19,7 @@ ms.workload:
 # Develop SharePoint solutions
   Several SharePoint project type templates are available in [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] for creating SharePoint sites and site elements. For a list of the available project types, see [SharePoint project and project item templates](../sharepoint/sharepoint-project-and-project-item-templates.md). Following is a description of the elements and properties of a SharePoint project.
 
- For information about SharePoint 2013 and SharePoint add-ins, see [SharePoint 2013](https://products.office.com/previous-versions/microsoft-sharepoint-2013) and [Build SharePoint add-ins](/sharepoint/dev/sp-add-ins/sharepoint-add-ins).
+ For information about SharePoint 2013 and SharePoint add-ins, see [SharePoint 2013](https://www.microsoft.com/microsoft-365/previous-versions/microsoft-sharepoint-2013) and [Build SharePoint add-ins](/sharepoint/dev/sp-add-ins/sharepoint-add-ins).
 
 ## Elements of a SharePoint project
  The nodes under a SharePoint project are known as *SharePoint items*. SharePoint items may also contain one or more subfiles, referred to as *SharePoint item files*, such as [!INCLUDE[TLA2#tla_xml](../sharepoint/includes/tla2sharptla-xml-md.md)] configuration files, .aspx forms, and more.

docs/sharepoint/getting-started-sharepoint-development-in-visual-studio.md

@@ -18,7 +18,7 @@ ms.workload:
 # Get started (SharePoint development in Visual Studio)
   This section helps you start working with [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] to develop SharePoint solutions that take advantage of [!INCLUDE[wss_14_long](../sharepoint/includes/wss-14-long-md.md)] and [!INCLUDE[moss_14_long](../sharepoint/includes/moss-14-long-md.md)].
 
- For information about SharePoint 2013 and SharePoint add-ins, see [SharePoint 2013](https://products.office.com/previous-versions/microsoft-sharepoint-2013) and [Build SharePoint add-ins](/sharepoint/dev/sp-add-ins/sharepoint-add-ins).
+ For information about SharePoint 2013 and SharePoint add-ins, see [SharePoint 2013](https://www.microsoft.com/microsoft-365/previous-versions/microsoft-sharepoint-2013) and [Build SharePoint add-ins](/sharepoint/dev/sp-add-ins/sharepoint-add-ins).
 
  SharePoint offers a Web-based collaboration platform. [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)] provides many project templates for creating SharePoint sites and content, including list definitions, workflows, business data connectivity models, and site definitions. In addition, you can create extensions for the SharePoint projects and tools in [!INCLUDE[vsprvs](../sharepoint/includes/vsprvs-md.md)].
 

docs/vs-2015/code-quality/ca2001-avoid-calling-problematic-methods.md

@@ -36,10 +36,10 @@ manager: "wpickett"
 
 |Method|Description|
 |------------|-----------------|
-|<xref:System.GC.Collect%2A?displayProperty=fullName>|Calling GC.Collect can significantly affect application performance and is rarely necessary. For more information, see the [Rico Mariani's Performance Tidbits](https://blogs.msdn.com/ricom/archive/2004/11/29/271829.aspx) blog entry on MSDN.|
+|<xref:System.GC.Collect%2A?displayProperty=fullName>|Calling GC.Collect can significantly affect application performance and is rarely necessary. For more information, see the [Rico Mariani's Performance Tidbits](https://docs.microsoft.com/archive/blogs/ricom/when-to-call-gc-collect) blog entry on MSDN.|
 |<xref:System.Threading.Thread.Resume%2A?displayProperty=fullName><br /><br /> <xref:System.Threading.Thread.Suspend%2A?displayProperty=fullName>|Thread.Suspend and Thread.Resume have been deprecated because of their unpredictable behavior.  Use other classes in the <xref:System.Threading> namespace, such as <xref:System.Threading.Monitor>, <xref:System.Threading.Mutex>, and <xref:System.Threading.Semaphore> to synchronize threads or protect resources.|
 |<xref:System.Runtime.InteropServices.SafeHandle.DangerousGetHandle%2A?displayProperty=fullName>|The DangerousGetHandle method poses a security risk because it can return a handle that is not valid. See the <xref:System.Runtime.InteropServices.SafeHandle.DangerousAddRef%2A> and the <xref:System.Runtime.InteropServices.SafeHandle.DangerousRelease%2A> methods for more information about how to use the DangerousGetHandle method safely.|
-|<xref:System.Reflection.Assembly.LoadFrom%2A?displayProperty=fullName><br /><br /> <xref:System.Reflection.Assembly.LoadFile%2A?displayProperty=fullName><br /><br /> <xref:System.Reflection.Assembly.LoadWithPartialName%2A?displayProperty=fullName>|These methods can load assemblies from unexpected locations. For example, see Suzanne Cook's .NET CLR Notes blog posts [LoadFile vs. LoadFrom](https://blogs.msdn.com/suzcook/archive/2003/09/19/loadfile-vs-loadfrom.aspx) and [Choosing a Binding Context](https://blogs.msdn.com/suzcook/archive/2003/05/29/57143.aspx) on the MSDN Web site for information about methods that load assemblies.|
+|<xref:System.Reflection.Assembly.LoadFrom%2A?displayProperty=fullName><br /><br /> <xref:System.Reflection.Assembly.LoadFile%2A?displayProperty=fullName><br /><br /> <xref:System.Reflection.Assembly.LoadWithPartialName%2A?displayProperty=fullName>|These methods can load assemblies from unexpected locations. For example, see Suzanne Cook's .NET CLR Notes blog posts [LoadFile vs. LoadFrom](https://docs.microsoft.com/archive/blogs/suzcook/loadfile-vs-loadfrom) and [Choosing a Binding Context](https://docs.microsoft.com/archive/blogs/suzcook/choosing-a-binding-context) on the MSDN Web site for information about methods that load assemblies.|
 |[CoSetProxyBlanket](https://msdn.microsoft.com/library/ms692692.aspx) (Ole32)<br /><br /> [CoInitializeSecurity](https://msdn.microsoft.com/library/ms693736.aspx) (Ole32)|By the time the user code starts executing in a managed process, it is too late to reliably call CoSetProxyBlanket. The common language runtime (CLR) takes initialization actions that may prevent the users P/Invoke from succeeding.<br /><br /> If you do have to call CoSetProxyBlanket for a managed application, we recommend that you start the process by using a native code (C++) executable, call CoSetProxyBlanket in the native code, and then start your managed code application in process. (Be sure to specify a runtime version number.)|
 
 ## How to Fix Violations

docs/vs-2015/debugger/debugging-gpu-code.md

@@ -79,4 +79,4 @@ You can debug C++ code that is running on the graphics processing unit (GPU). GP
 ## See Also  
  [Walkthrough: Debugging a C++ AMP Application](https://msdn.microsoft.com/library/40e92ecc-f6ba-411c-960c-b3047b854fb5)   
  [Project Settings for a C++ Debug Configuration](../debugger/project-settings-for-a-cpp-debug-configuration.md)   
- [Start GPU Debugging in Visual Studio](https://blogs.msdn.com/b/nativeconcurrency/archive/2012/03/17/start-gpu-debugging-in-visual-studio-11.aspx)
+ [Start GPU Debugging in Visual Studio](https://docs.microsoft.com/archive/blogs/nativeconcurrency/start-gpu-debugging-in-visual-studio-2012)

docs/vs-2015/debugger/intellitrace.md

@@ -180,7 +180,7 @@ You can spend less time debugging your application when you use IntelliTrace to
  [Using saved IntelliTrace data](../debugger/using-saved-intellitrace-data.md)  
 
 ### Blogs  
- [Visual Studio ALM + Team Foundation Server](https://blogs.msdn.com/b/visualstudioalm)  
+ [Visual Studio ALM + Team Foundation Server](https://devblogs.microsoft.com/devops/welcome-to-the-visual-studio-alm-team-foundation-server-blog/)  
 
 ### Forums  
  [Visual Studio Diagnostics](https://social.msdn.microsoft.com/Forums/vsdebug)

docs/vs-2015/debugger/using-the-intellitrace-stand-alone-collector.md

@@ -220,7 +220,7 @@ The **IntelliTrace stand-alone collector** lets you collect IntelliTrace diagnos
     |||
     |-|-|
     |*ApplicationPool*|The name of the application pool where your application runs|
-    |*PathToCollectionPlan*|The path to a collection plan, an .xml file that configures settings for the collector.<br /><br /> You can specify a plan that comes with the collector. The following plans work for Web apps and SharePoint applications:<br /><br /> -   collection_plan.ASP.NET.default.xml<br />     Collects only IntelliTrace events and SharePoint events, including exceptions, database calls, and Web server requests.<br />-   collection_plan.ASP.NET.trace.xml<br />     Collects function calls and all the data in collection_plan.ASP.NET.default.xml. This plan is good for detailed analysis, but it might slow down your app more than collection_plan.ASP.NET.default.xml.<br /><br /> To avoid slowing down your app, customize these plans or create your own plan. For security, put any custom plans in the same secure location as the collector files. See [Creating and Customizing IntelliTrace Collection Plans](https://blogs.msdn.com/b/visualstudioalm/archive/2011/09/15/modifying-an-intellitrace-collection-plan-for-the-stand-alone-collector.aspx) and [How do I get the most data without slowing down my app?](#Minimizing) **Note:**  By default, the max size of the .iTrace file is 100 MB. When the .iTrace file reaches this limit, the collector deletes the file’s earliest entries to make space for newer entries. To change this limit, edit the collection plan’s `MaximumLogFileSize` attribute. <br /><br /> *Where can I find localized versions of these collection plans?*<br /><br /> You can find localized plans in the collector's subfolders.|
+    |*PathToCollectionPlan*|The path to a collection plan, an .xml file that configures settings for the collector.<br /><br /> You can specify a plan that comes with the collector. The following plans work for Web apps and SharePoint applications:<br /><br /> -   collection_plan.ASP.NET.default.xml<br />     Collects only IntelliTrace events and SharePoint events, including exceptions, database calls, and Web server requests.<br />-   collection_plan.ASP.NET.trace.xml<br />     Collects function calls and all the data in collection_plan.ASP.NET.default.xml. This plan is good for detailed analysis, but it might slow down your app more than collection_plan.ASP.NET.default.xml.<br /><br /> To avoid slowing down your app, customize these plans or create your own plan. For security, put any custom plans in the same secure location as the collector files. See [Creating and Customizing IntelliTrace Collection Plans](https://devblogs.microsoft.com/devops/modifying-an-intellitrace-collection-plan-for-the-stand-alone-collector/) and [How do I get the most data without slowing down my app?](#Minimizing) **Note:**  By default, the max size of the .iTrace file is 100 MB. When the .iTrace file reaches this limit, the collector deletes the file’s earliest entries to make space for newer entries. To change this limit, edit the collection plan’s `MaximumLogFileSize` attribute. <br /><br /> *Where can I find localized versions of these collection plans?*<br /><br /> You can find localized plans in the collector's subfolders.|
     |*FullPathToITraceFileDirectory*|The full path to the .iTrace file directory. **Security Note:**  Provide the full path, not a relative path.|
 
      The collector attaches to the application pool and starts collecting data.
@@ -259,7 +259,7 @@ The **IntelliTrace stand-alone collector** lets you collect IntelliTrace diagnos
     |||
     |-|-|
     |*FullPathToIntelliTraceCollectorExecutable*|The full path to the collector executable, IntelliTraceSC.exe|
-    |*PathToCollectionPlan*|The path to a collection plan, an .xml file that configures settings for the collector.<br /><br /> You can specify a plan that comes with the collector. The following plans work for managed apps:<br /><br /> -   collection_plan.ASP.NET.default.xml<br />     Collects IntelliTrace events only, including exceptions, database calls, and Web server requests.<br />-   collection_plan.ASP.NET.trace.xml<br />     Collects function calls and all the data in collection_plan.ASP.NET.default.xml. This plan is good for detailed analysis, but it might slow down your app more than collection_plan.ASP.NET.default.xml.<br /><br /> To avoid slowing down your app, customize these plans or create your own plan. For security, put any custom plans in the same secure location as the collector files. See [Creating and Customizing IntelliTrace Collection Plans](https://blogs.msdn.com/b/visualstudioalm/archive/2011/09/15/modifying-an-intellitrace-collection-plan-for-the-stand-alone-collector.aspx) and [How do I get the most data without slowing down my app?](#Minimizing) **Note:**  By default, the max size of the .iTrace file is 100 MB. When the .iTrace file reaches this limit, the collector deletes the file’s earliest entries to make space for newer entries. To change this limit, edit the collection plan’s `MaximumLogFileSize` attribute. <br /><br /> *Where can I find localized versions of these collection plans?*<br /><br /> You can find localized plans in the collector's subfolders.|
+    |*PathToCollectionPlan*|The path to a collection plan, an .xml file that configures settings for the collector.<br /><br /> You can specify a plan that comes with the collector. The following plans work for managed apps:<br /><br /> -   collection_plan.ASP.NET.default.xml<br />     Collects IntelliTrace events only, including exceptions, database calls, and Web server requests.<br />-   collection_plan.ASP.NET.trace.xml<br />     Collects function calls and all the data in collection_plan.ASP.NET.default.xml. This plan is good for detailed analysis, but it might slow down your app more than collection_plan.ASP.NET.default.xml.<br /><br /> To avoid slowing down your app, customize these plans or create your own plan. For security, put any custom plans in the same secure location as the collector files. See [Creating and Customizing IntelliTrace Collection Plans](https://devblogs.microsoft.com/devops/modifying-an-intellitrace-collection-plan-for-the-stand-alone-collector/) and [How do I get the most data without slowing down my app?](#Minimizing) **Note:**  By default, the max size of the .iTrace file is 100 MB. When the .iTrace file reaches this limit, the collector deletes the file’s earliest entries to make space for newer entries. To change this limit, edit the collection plan’s `MaximumLogFileSize` attribute. <br /><br /> *Where can I find localized versions of these collection plans?*<br /><br /> You can find localized plans in the collector's subfolders.|
     |*FullPathToITraceFileDirectoryAndFileName*|The full path to the .iTrace file directory and the .iTrace file name with the **.itrace** extension. **Security Note:**  Provide the full path, not a relative path.|
     |*PathToAppExecutableFileAndFileName*|The path and file name of your managed app|
 
@@ -282,7 +282,7 @@ The **IntelliTrace stand-alone collector** lets you collect IntelliTrace diagnos
     > To debug with IntelliTrace and step through code, you must have the matching source files and symbol files on your development machine. See [Diagnose problems after deployment](../debugger/diagnose-problems-after-deployment.md).
 
 ## <a name="Minimizing"></a> How do I get the most data without slowing down my app?
- IntelliTrace can collect lots of data, so the impact on your app's performance depends on the data that IntelliTrace collects and the kind of code it analyzes. See [Optimizing IntelliTrace Collection on Production Servers](https://blogs.msdn.com/b/visualstudioalm/archive/2012/05/18/optimizing-intellitrace-collection-on-production-server.aspx).
+ IntelliTrace can collect lots of data, so the impact on your app's performance depends on the data that IntelliTrace collects and the kind of code it analyzes. See [Optimizing IntelliTrace Collection on Production Servers](https://devblogs.microsoft.com/devops/optimizing-intellitrace-collection-on-production-server/).
 
  Here are some ways to get the most data without slowing down your app:
 
@@ -385,13 +385,13 @@ The **IntelliTrace stand-alone collector** lets you collect IntelliTrace diagnos
  [IntelliTrace](../debugger/intellitrace.md)
 
 ### Blogs
- [Using the IntelliTrace Standalone Collector Remotely](https://blogs.msdn.com/b/visualstudioalm/archive/2012/07/09/using-the-intellitrace-standalone-collector-remotely.aspx)
+ [Using the IntelliTrace Standalone Collector Remotely](https://devblogs.microsoft.com/devops/using-the-intellitrace-standalone-collector-remotely/)
 
- [Creating and Customizing IntelliTrace Collection Plans](https://blogs.msdn.com/b/visualstudioalm/archive/2011/09/15/modifying-an-intellitrace-collection-plan-for-the-stand-alone-collector.aspx)
+ [Creating and Customizing IntelliTrace Collection Plans](https://devblogs.microsoft.com/devops/modifying-an-intellitrace-collection-plan-for-the-stand-alone-collector/)
 
- [Optimizing IntelliTrace Collection on Production Servers](https://blogs.msdn.com/b/visualstudioalm/archive/2012/05/18/optimizing-intellitrace-collection-on-production-server.aspx)
+ [Optimizing IntelliTrace Collection on Production Servers](https://devblogs.microsoft.com/devops/optimizing-intellitrace-collection-on-production-server/)
 
- [Visual Studio ALM + TFS Blog](https://blogs.msdn.com/b/visualstudioalm)
+ [Visual Studio ALM + TFS Blog](https://devblogs.microsoft.com/devops/welcome-to-the-visual-studio-alm-team-foundation-server-blog/)
 
 ### Forums
  [Visual Studio Debugger](https://social.msdn.microsoft.com/Forums/vsdebug)