Merge pull request #14017 from Mikejo5000/mikejo-link-fixes-2

Stacyrch140 · web-flow · commit b92a541419f3 · 2025-06-25T18:13:05.000-04:00
Update links to redirected URLs
diff --git a/docs/help-viewer/administrator-guide.md b/docs/help-viewer/administrator-guide.md
@@ -16,7 +16,7 @@ In this article, you learn to use the Help Viewer to deploy and manage local Hel
 
 If your network environment allows clients to access the internet, you can use the **Help Content Manager** executable to deploy local Help content from the internet. For more information about *HlpCtntMgr.exe* command line syntax, see [Command-line arguments for the Help Content Manager](../help-viewer/command-line-arguments.md).
 
-For information about creating content, creating an intranet service endpoint, and similar types of activities, see the [Help Viewer SDK](../extensibility/internals/microsoft-help-viewer-sdk.md).
+For information about creating content, creating an intranet service endpoint, and similar types of activities, see the [Help Viewer SDK](/previous-versions/visualstudio/visual-studio-2017/extensibility/internals/microsoft-help-viewer-sdk).
 
 If you do not have internet access in your network environment, Help Viewer can deploy local Help content from the intranet or a network share. You can also disable Visual Studio IDE Help options by using [registry key overrides](../help-viewer/behavior-overrides.md) for functionality such as:
 
@@ -142,4 +142,4 @@ Next, you need to package the content so it can be deployed to client computers.
 - [Command-line arguments for the Help Content Manager](../help-viewer/command-line-arguments.md)
 - [Override Help Viewer defaults](../help-viewer/behavior-overrides.md)
 - [Microsoft Help Viewer](../help-viewer/overview.md)
-- [Help Viewer SDK](../extensibility/internals/microsoft-help-viewer-sdk.md)
+- [Help Viewer SDK](/previous-versions/visualstudio/visual-studio-2017/extensibility/internals/microsoft-help-viewer-sdk)
diff --git a/docs/help-viewer/find-topics.md b/docs/help-viewer/find-topics.md
@@ -98,7 +98,7 @@ You might enter a search string that includes multiple words, such as "word1 wor
 
 > [!IMPORTANT]
 > - Phrase searches are not supported. If you specify more than one word in a search string, returned topics contain all the words that you specified but not necessarily the exact phrase that you specified.
-> - Use logical operators to specify the relationship between words in your search phrase. You can include logical operators, such as AND, OR, NOT, and NEAR, to further refine your search. For example, if you search for "declaring NEAR union", search results include topics that contain the words "declaring" and "union" no more than a few words apart from each other. For more information, see [Logical operators in search expressions](../help-viewer/logical-operators-search-expressions.md).
+> - Use logical operators to specify the relationship between words in your search phrase. You can include logical operators, such as AND, OR, NOT, and NEAR, to further refine your search. For example, if you search for "declaring NEAR union", search results include topics that contain the words "declaring" and "union" no more than a few words apart from each other.
 
 ### Filters
 
diff --git a/docs/msbuild/creating-forwarding-loggers.md b/docs/msbuild/creating-forwarding-loggers.md
@@ -33,10 +33,10 @@ Forwarding loggers improve logging efficiency by letting you choose the events y
 
 ## Multi-processor-aware loggers
 
- When you build a project on a multi-processor system, the build messages from each processor are not automatically interleaved in a unified sequence. Instead, you must establish a message grouping priority by using the <xref:Microsoft.Build.Framework.BuildEventContext> class that is attached to every message. For more information about multi-processor building, see [Logging in a multi-processor environment](../msbuild/logging-in-a-multi-processor-environment.md).
+ When you build a project on a multi-processor system, the build messages from each processor are not automatically interleaved in a unified sequence. Instead, you must establish a message grouping priority by using the <xref:Microsoft.Build.Framework.BuildEventContext> class that is attached to every message. For more information about multi-processor building, see [Logging in a multi-processor environment](writing-multi-processor-aware-loggers.md).
 
 ## Related content
 
 - [Obtain build logs](../msbuild/obtaining-build-logs-with-msbuild.md)
 - [Build loggers](../msbuild/build-loggers.md)
-- [Logging in a multi-processor environment](../msbuild/logging-in-a-multi-processor-environment.md)
+- [Logging in a multi-processor environment](writing-multi-processor-aware-loggers.md)
diff --git a/docs/msbuild/msbuild-errors.md b/docs/msbuild/msbuild-errors.md
@@ -109,4 +109,3 @@ We're sorry! It looks like we couldn't find what you were looking for.
 - Use the [Microsoft Learn](/) toolbar to search 
 - Browse the Knowledge Base for [Visual Studio troubleshooting](/troubleshoot/visualstudio/welcome-visual-studio/)
 
-**Didn't mean to click?** [Remap or disable the `F1` help key](../ide/not-in-toc/change-f1-help-key.md)
diff --git a/docs/msbuild/msbuild-multitargeting-overview.md b/docs/msbuild/msbuild-multitargeting-overview.md
@@ -45,4 +45,4 @@ By using MSBuild, you can compile an application to run on any one of several ve
 
 ## Troubleshooting
 
- You might encounter errors if you try to reference an assembly that is not part of the target context. For more information about these errors and what to do about them, see [Troubleshoot .NET Framework targeting errors](../msbuild/troubleshooting-dotnet-framework-targeting-errors.md).
+ You might encounter errors if you try to reference an assembly that is not part of the target context. For more information about these errors and what to do about them, see [Troubleshoot .NET Framework targeting errors](/troubleshoot/developer/visualstudio/project-build/troubleshooting-dotnet-framework-targeting-errors).
diff --git a/docs/msbuild/obtaining-build-logs-with-msbuild.md b/docs/msbuild/obtaining-build-logs-with-msbuild.md
@@ -101,6 +101,6 @@ For more information, see [Command-line reference](../msbuild/msbuild-command-li
 
 - <xref:Microsoft.Build.Framework.LoggerVerbosity>
 - [Build loggers](../msbuild/build-loggers.md)
-- [Logging in a multi-processor environment](../msbuild/logging-in-a-multi-processor-environment.md)
+- [Logging in a multi-processor environment](writing-multi-processor-aware-loggers.md)
 - [Creating forwarding loggers](../msbuild/creating-forwarding-loggers.md)
 - [MSBuild concepts](../msbuild/msbuild-concepts.md)
diff --git a/docs/msbuild/what-s-new-in-msbuild-15-0.md b/docs/msbuild/what-s-new-in-msbuild-15-0.md
@@ -16,7 +16,7 @@ MSBuild is now available as part of the [.NET Core SDK](https://dotnet.microsoft
 
  MSBuild is now installed in a folder under each version of Visual Studio. For example, *C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild*. You can also use the following PowerShell module to locate MSBuild: [vssetup.powershell](https://github.com/Microsoft/vssetup.powershell).
 
- MSBuild is no longer installed in the Global Assembly Cache. To reference MSBuild programmatically, use NuGet packages. For more information, see [Updating an existing application for MSBuild 15.0](../msbuild/updating-an-existing-application.md).
+ MSBuild is no longer installed in the Global Assembly Cache. To reference MSBuild programmatically, use NuGet packages. 
 
 ## Changed properties
 

Original file line number	Diff line number	Diff line change
`@@ -109,4 +109,3 @@ We're sorry! It looks like we couldn't find what you were looking for.`
`109`	`109`	`- Use the [Microsoft Learn](/) toolbar to search`
`110`	`110`	`- Browse the Knowledge Base for [Visual Studio troubleshooting](/troubleshoot/visualstudio/welcome-visual-studio/)`
`111`	`111`
`112`		-Didn't mean to click? [Remap or disable the `F1` help key](../ide/not-in-toc/change-f1-help-key.md)
Original file line number	Diff line number	Diff line change
`@@ -45,4 +45,4 @@ By using MSBuild, you can compile an application to run on any one of several ve`
`45`	`45`
`46`	`46`	`## Troubleshooting`
`47`	`47`
`48`		`- You might encounter errors if you try to reference an assembly that is not part of the target context. For more information about these errors and what to do about them, see [Troubleshoot .NET Framework targeting errors](../msbuild/troubleshooting-dotnet-framework-targeting-errors.md).`
	`48`	`+ You might encounter errors if you try to reference an assembly that is not part of the target context. For more information about these errors and what to do about them, see [Troubleshoot .NET Framework targeting errors](/troubleshoot/developer/visualstudio/project-build/troubleshooting-dotnet-framework-targeting-errors).`