Fix links discovered by using link-checking tooling (#723)

* Add link-checker to devcontainer

* Add settings for link checker

* Fix a URL redirect

* Fix a redirect

* Fix a redirect

* Fix a redirect

* Fix a redirect

* fix redirects

* Ignore common URL

* remove "www" subdomain from nunit.org URLs

* reflect new default branch name

* Add common URL

* fix broken link

* more fixe

* fixes

* Ignore VS marketplace

They return 404s instead of 429s, etc.

* fixes

* move stuff around a bit

* remove link-checker

Not supported anymore really.

docs/articles/nunit-engine/Getting-Started.md

@@ -14,7 +14,7 @@ The actual engine itself is contained within the `nunit.engine` assembly, and it
 
 ## Packages
 
-The NUnit Engine can be found in the [NUnit.Engine NuGet Package](https://www.nuget.org/packages/NUnit.Engine/). It is also included within the .zip file found in [nunit-console repository](https://github.com/nunit/nunit-console/releases]) releases.
+The NUnit Engine can be found in the [NUnit.Engine NuGet Package](https://www.nuget.org/packages/NUnit.Engine/). It is also included within the .zip file found in [nunit-console repository](https://github.com/nunit/nunit-console/releases) releases.
 
 ## Using the API
 

docs/articles/nunit-engine/Test-Engine-API.md

@@ -8,7 +8,7 @@ The NUnit Test Engine API is our published API for discovering, exploring and ex
 
 ## Overview
 
-The static class [TestEngineActivator](https://github.com/nunit/nunit-console/blob/master/src/NUnitEngine/nunit.engine.api/TestEngineActivator.cs) is used to get an interface to the engine. Its `CreateInstance` member has two overloads, depending on whether a particular minimum version of the engine is required.
+The static class [TestEngineActivator](https://github.com/nunit/nunit-console/blob/main/src/NUnitEngine/nunit.engine.api/TestEngineActivator.cs) is used to get an interface to the engine. Its `CreateInstance` member has two overloads, depending on whether a particular minimum version of the engine is required.
 
 ```csharp
 public static ITestEngine CreateInstance(bool unused = false);
@@ -210,12 +210,12 @@ The following services are available publicly.
 
 | Service            | Interface    | Function  |
 |--------------------|--------------|-----------|
-| ExtensionService   | [IExtensionService](https://github.com/nunit/nunit-console/blob/master/src/NUnitEngine/nunit.engine.api/IExtensionService.cs) | Manages engine extensions |
-| RecentFilesService | [IRecentFiles](https://github.com/nunit/nunit-console/blob/master/src/NUnitEngine/nunit.engine.api/IRecentFiles.cs)  | Provides information about recently opened files  |
-| ResultService      | [IResultService](https://github.com/nunit/nunit-console/blob/master/src/NUnitEngine/nunit.engine.api/IResultService.cs)  | Produces test result output in various formats  |
-| SettingsService    | [ISettings](https://github.com/nunit/nunit-console/blob/master/src/NUnitEngine/nunit.engine.api/ISettings.cs) | Provides access to user settings |
-| TestFilterService  | [ITestFilterService](https://github.com/nunit/nunit-console/blob/master/src/NUnitEngine/nunit.engine.api/ITestFilterService.cs) | Creates properly formed test filters for use by runners |
-| LoggingService     | [ILogging](https://github.com/nunit/nunit-console/blob/master/src/NUnitEngine/nunit.engine.api/ILogging.cs) | Provides centralized internal trace logging for both the engine and runners (Not Yet Implemented) |
+| ExtensionService   | [IExtensionService](https://github.com/nunit/nunit-console/blob/main/src/NUnitEngine/nunit.engine.api/IExtensionService.cs) | Manages engine extensions |
+| RecentFilesService | [IRecentFiles](https://github.com/nunit/nunit-console/blob/main/src/NUnitEngine/nunit.engine.api/IRecentFiles.cs)  | Provides information about recently opened files  |
+| ResultService      | [IResultService](https://github.com/nunit/nunit-console/blob/main/src/NUnitEngine/nunit.engine.api/IResultService.cs)  | Produces test result output in various formats  |
+| SettingsService    | [ISettings](https://github.com/nunit/nunit-console/blob/main/src/NUnitEngine/nunit.engine.api/ISettings.cs) | Provides access to user settings |
+| TestFilterService  | [ITestFilterService](https://github.com/nunit/nunit-console/blob/main/src/NUnitEngine/nunit.engine.api/ITestFilterService.cs) | Creates properly formed test filters for use by runners |
+| LoggingService     | [ILogging](https://github.com/nunit/nunit-console/blob/main/src/NUnitEngine/nunit.engine.api/ILogging.cs) | Provides centralized internal trace logging for both the engine and runners (Not Yet Implemented) |
 
 The following services are used internally by the engine but are not currently exposed publicly. They potentially could be in the future:
 

docs/articles/nunit-engine/release-notes.md

@@ -500,7 +500,7 @@ aggregate NuGet packages also include updated versions of several extensions.
 ## Earlier Releases
 
 * Release Notes for [NUnit 2.9.1 through 3.5](xref:pre35releasenotes).
-* Release Notes for [NUnit 2.6 through 2.6.4](https://www.nunit.org/?p=releaseNotes&r=2.6.4)
-* Release Notes for [NUnit 2.5 through 2.5.10](https://www.nunit.org/?p=releaseNotes&r=2.5.10)
-* Release Notes for [NUnit 2.4 through 2.4.8](https://www.nunit.org/?p=releaseNotes&r=2.4.8)
-* Release Notes for [NUnit 2.0 through 2.2.10](https://www.nunit.org/?p=releaseNotes&r=2.2.10)
+* Release Notes for [NUnit 2.6 through 2.6.4](https://nunit.org/?p=releaseNotes&r=2.6.4)
+* Release Notes for [NUnit 2.5 through 2.5.10](https://nunit.org/?p=releaseNotes&r=2.5.10)
+* Release Notes for [NUnit 2.4 through 2.4.8](https://nunit.org/?p=releaseNotes&r=2.4.8)
+* Release Notes for [NUnit 2.0 through 2.2.10](https://nunit.org/?p=releaseNotes&r=2.2.10)

docs/articles/nunit/extending-nunit/Framework-Extensibility.md

@@ -14,4 +14,4 @@ In this documentation, we refer to three different types of Framework extension:
 
 ### On Custom constraints
 
-[How to extend the NUnit constraints](http://hermit.no/how-to-extend-the-nunit-constraints/)
+[How to extend the NUnit constraints](https://hermit.no/how-to-extend-the-nunit-constraints/)

docs/articles/nunit/getting-started/dotnet-core-and-dotnet-standard.md

@@ -44,7 +44,7 @@ Or you can specify the csproj file you want to test
   dotnet test .\test\NetCore10Tests\NetCore10Tests.csproj
 ```
 
-For a more complete walk-through, please see [Testing .NET Core with NUnit in Visual Studio 2017](https://www.alteridem.net/2017/05/04/test-net-core-nunit-vs2017/)
+For a more complete walk-through, please see [Testing .NET Core with NUnit in Visual Studio 2017](https://alteridem.net/2017/05/04/test-net-core-nunit-vs2017/)
 
 ## Using the NUnit project templates
 

docs/articles/nunit/release-notes/Pre-3.5-Release-Notes.md

@@ -1154,7 +1154,7 @@ use the NUnit NuGet packages for the framework, but a ZIP file with the binaries
 
 ## Earlier Releases
 
-* Release Notes for [NUnit 2.6 through 2.6.4](https://www.nunit.org/?p=releaseNotes&r=2.6.4)
-* Release Notes for [NUnit 2.5 through 2.5.10](https://www.nunit.org/?p=releaseNotes&r=2.5.10)
-* Release Notes for [NUnit 2.4 through 2.4.8](https://www.nunit.org/?p=releaseNotes&r=2.4.8)
-* Release Notes for [NUnit 2.0 through 2.2.10](https://www.nunit.org/?p=releaseNotes&r=2.2.10)
+* Release Notes for [NUnit 2.6 through 2.6.4](https://nunit.org/?p=releaseNotes&r=2.6.4)
+* Release Notes for [NUnit 2.5 through 2.5.10](https://nunit.org/?p=releaseNotes&r=2.5.10)
+* Release Notes for [NUnit 2.4 through 2.4.8](https://nunit.org/?p=releaseNotes&r=2.4.8)
+* Release Notes for [NUnit 2.0 through 2.2.10](https://nunit.org/?p=releaseNotes&r=2.2.10)

docs/articles/nunit/release-notes/framework.md

@@ -829,7 +829,7 @@ This release of the framework no longer includes builds for Compact Framework or
 ## Earlier Releases
 
 * Release Notes for [NUnit 2.9.1 through 3.5](xref:pre35releasenotes)
-* Release Notes for [NUnit 2.6 through 2.6.4](https://www.nunit.org/?p=releaseNotes&r=2.6.4)
-* Release Notes for [NUnit 2.5 through 2.5.10](https://www.nunit.org/?p=releaseNotes&r=2.5.10)
-* Release Notes for [NUnit 2.4 through 2.4.8](https://www.nunit.org/?p=releaseNotes&r=2.4.8)
-* Release Notes for [NUnit 2.0 through 2.2.10](https://www.nunit.org/?p=releaseNotes&r=2.2.10)
+* Release Notes for [NUnit 2.6 through 2.6.4](https://nunit.org/?p=releaseNotes&r=2.6.4)
+* Release Notes for [NUnit 2.5 through 2.5.10](https://nunit.org/?p=releaseNotes&r=2.5.10)
+* Release Notes for [NUnit 2.4 through 2.4.8](https://nunit.org/?p=releaseNotes&r=2.4.8)
+* Release Notes for [NUnit 2.0 through 2.2.10](https://nunit.org/?p=releaseNotes&r=2.2.10)

docs/articles/nunit/running-tests/Template-Based-Test-Naming.md

@@ -24,7 +24,7 @@ However, if you're out on your own, the naming *can* be overridden by the user i
 
 * `{a}` The full argument representation, enclosed in parentheses and separated by commas. Each argument is represented by the standard NUnit format for certain types, otherwise by the result of ToString().
 
-* `{p}` Same as `{a}` but with a parameter name before each argument in the same style as the [*named arguments* C# language feature](https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/classes-and-structs/named-and-optional-arguments#named-arguments).
+* `{p}` Same as `{a}` but with a parameter name before each argument in the same style as the [*named arguments* C# language feature](https://learn.microsoft.com/en-us/dotnet/csharp/programming-guide/classes-and-structs/named-and-optional-arguments#named-arguments).
 
 * `{0}`, `{1}`...`{9}`. An individual argument. This form is only useful when setting the name of an individual test case. If used in the default format string, any arguments not used will be ignored.
 

docs/articles/nunit/running-tests/Test-Selection-Language.md

@@ -59,7 +59,7 @@ The right-hand side of the comparison may be a sequence of non-blank, non-specia
 
 For matching regular expressions, NUnit uses .NET's `Regex.IsMatch` method. For detailed information on the syntax of regular expressions in .NET, see [Regular Expressions in .NET](https://docs.microsoft.com/dotnet/standard/base-types/regular-expression-language-quick-reference).
 
-For specifying qualified names, the same format as used for reflection should be used. For example `My.Name.Space.TestFixture+NestedFixture` can be used to select a nested fixture. For detailed information see: [Specifying Special Characters](https://docs.microsoft.com/dotnet/framework/reflection-and-codedom/specifying-fully-qualified-type-names#specifying-special-characters)
+For specifying qualified names, the same format as used for reflection should be used. For example `My.Name.Space.TestFixture+NestedFixture` can be used to select a nested fixture. For detailed information see: [Specifying Special Characters](https://learn.microsoft.com/en-us/dotnet/framework/reflection-and-codedom/specifying-fully-qualified-type-names#specifying-special-characters)
 
 ## Filtering By Namespace
 

docs/articles/nunit/writing-tests/Randomizer-Methods.md

@@ -208,4 +208,4 @@ Returns a random string of the specified length using the characters in the stri
 
 ### `NextGuid()` (available in version 3.8)
 
-Generates a version 4 Guid conforming the [RFC 4122](https://tools.ietf.org/html/rfc4122#section-4.4). Version 4 Guids are made of random data.
+Generates a version 4 Guid conforming the [RFC 4122](https://www.rfc-editor.org/rfc/rfc4122#section-4.4). Version 4 Guids are made of random data.

docs/articles/nunit/writing-tests/attributes/apartment.md

@@ -5,7 +5,7 @@ uid: apartment-attribute
 # Apartment
 
 The `ApartmentAttribute` is used on a test method, class or assembly
-to specify that the tests should be run in a particular [apartment](https://docs.microsoft.com/en-us/windows/desktop/com/processes--threads--and-apartments), either
+to specify that the tests should be run in a particular [apartment](https://learn.microsoft.com/en-us/windows/win32/com/processes--threads--and-apartments), either
 the STA or the MTA.
 
 When running tests in parallel, the test is simply scheduled to execute

docs/articles/vs-test-adapter/AdapterV3-Release-Notes.md

@@ -37,7 +37,7 @@ See [here for all details](/articles/vs-test-adapter/Tips-And-Tricks.html) on th
 
 ## NUnit3 Test Adapter for Visual Studio - Version 3.17.0-beta.2 - June 8, 2020
 
-This is the 2nd beta for 3.17, published on [Nuget](https://nuget.org).
+This is the 2nd beta for 3.17, published on [Nuget](https://www.nuget.org/).
 
 ### Features and Enhancements
 
@@ -59,7 +59,7 @@ This is the 2nd beta for 3.17, published on [Nuget](https://nuget.org).
 
 ## NUnit3 Test Adapter for Visual Studio - Version 3.17.0-beta.1 - April 19, 2020
 
-This is the first beta release published on [Nuget](https://nuget.org).
+This is the first beta release published on [Nuget](https://www.nuget.org/).
 
 It contains new features and some bugfixes.
 
@@ -188,7 +188,7 @@ This release focuses on producing NUnit test result XML which can be useful when
 
 The VSIX is also made compatible with the upcoming VS 2019. Please note support for the VSIX is being deprecated in Visual Studio, and we strongly recommend you to change your test projects to use the [NuGet adapter version](https://www.nuget.org/packages/NUnit3TestAdapter/).
 
-The [NUnit internal properties](https://github.com/nunit/nunit/blob/master/src/NUnitFramework/framework/Internal/PropertyNames.cs) have been "over-populating" in the Test Explorer.  These are now filtered out, although you may still see these when you have [Source Based Discovery (SBD)](https://docs.microsoft.com/en-us/visualstudio/test/test-explorer-faq?view=vs-2017) turned on (which is the default in VS).  Once you have run, they will be gone. We expect this part of the issue (SBD) to be fixed in VS.
+The [NUnit internal properties](https://github.com/nunit/nunit/blob/master/src/NUnitFramework/framework/Internal/PropertyNames.cs) have been "over-populating" in the Test Explorer.  These are now filtered out, although you may still see these when you have [Source Based Discovery (SBD)](https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2017/test/test-explorer-faq?view=vs-2017) turned on (which is the default in VS).  Once you have run, they will be gone. We expect this part of the issue (SBD) to be fixed in VS.
 
 If you still want to see the properties, you can enable that again setting a runsettings property `ShowInternalProperties` to true.
 
@@ -252,7 +252,7 @@ This is a hotfix release to fix the duplicated traits issue.
 
 ### Features
 
-* [PR 500](https://github.com/nunit/nunit3-vs-adapter/pull/500) NUnit3VsAdapter to support managed sources only based on [RFC](https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0020-Improving-Logic-To-Pass-Sources-To-Adapters.md)  (Thanks to [mayankbansal018](https://github.com/mayankbansal018) for this PR)
+* [PR 500](https://github.com/nunit/nunit3-vs-adapter/pull/500) NUnit3VsAdapter to support managed sources only based on [RFC](https://github.com/Microsoft/vstest-docs/blob/main/RFCs/0020-Improving-Logic-To-Pass-Sources-To-Adapters.md)  (Thanks to [mayankbansal018](https://github.com/mayankbansal018) for this PR)
 
 * [543](https://github.com/nunit/nunit3-vs-adapter/issues/543) Adapter should pass `Error` and `Progress` messages to vstest engine as well as stdOut messages (Thanks to [NikolayPianikov](https://github.com/NikolayPianikov) for [PR 544](https://github.com/nunit/nunit3-vs-adapter/pull/544)). Also fixes this [TeamCity issue](https://youtrack.jetbrains.com/issue/TW-55900)  
 
@@ -338,10 +338,10 @@ This version supports Visual Studio from version 2012, Update 1 and upwards, and
 
 ### Features
 
-* The adapter now support running .net core projects. See [this post](https://www.alteridem.net/2017/05/04/test-net-core-nunit-vs2017/) for details.  Note: Only supported by the nuget adapter, not the vsix.
+* The adapter now support running .net core projects. See [this post](https://alteridem.net/2017/05/04/test-net-core-nunit-vs2017/) for details.  Note: Only supported by the nuget adapter, not the vsix.
 * The adapter now uses version 3.7 of the engine to run tests ([360](https://github.com/nunit/nunit3-vs-adapter/issues/360))
 * Attachments can be added to tests ([358](https://github.com/nunit/nunit3-vs-adapter/issues/358))
-* Prepared for new  upcoming Test Explorer functionality, as documented in this [RFC](https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0010-Source-Information-For-Discovered-Tests.md)  ([351](https://github.com/nunit/nunit3-vs-adapter/issues/351))
+* Prepared for new  upcoming Test Explorer functionality, as documented in this [RFC](https://github.com/Microsoft/vstest-docs/blob/main/RFCs/0010-Source-Information-For-Discovered-Tests.md)  ([351](https://github.com/nunit/nunit3-vs-adapter/issues/351))
 
 ### Resolved Issues
 

docs/articles/vs-test-adapter/Debugging.md

@@ -21,8 +21,8 @@ dotnet test -- NUnit.DebugExecution=true
 
 If you want to do this using Visual Studio, you must add a runsettings file, and add these settings there to the NUnit section.
 
-A detailed explanation of the process can be found in [this blog post](http://hermit.no/debugging-the-nunit3testadapter-take-2/)
+A detailed explanation of the process can be found in [this blog post](https://hermit.no/debugging-the-nunit3testadapter-take-2/)
 
 ## Debugging earlier versions
 
-See [this blog post](http://hermit.no/debugging-the-nunit3testadapter/) for details on that process.
+See [this blog post](https://hermit.no/debugging-the-nunit3testadapter/) for details on that process.

docs/articles/vs-test-adapter/Resources.md

@@ -2,7 +2,7 @@
 
 ## Further information
 
-For more information see the blogs by [Charlie Poole](http://nunit.com/blogs/), [Rob Prouse](https://www.alteridem.net/) and [Terje Sandstrom](http://hermit.no)
+For more information see the blogs by [Charlie Poole](http://nunit.com/articles/), [Rob Prouse](https://alteridem.net/) and [Terje Sandstrom](https://hermit.no)
 
 The MSDN ALM blog post series on _How to Manage Unit Tests in Visual Studio 2012 Update 1_ is useful for later versions as well:
 
@@ -12,7 +12,7 @@ The MSDN ALM blog post series on _How to Manage Unit Tests in Visual Studio 2012
 
 * [Part 3: Unit testing with Traits and code coverage in Visual Studio 2012 using the TFS Build](https://devblogs.microsoft.com/devops/part-3-unit-testing-with-traits-and-code-coverage-in-visual-studio-2012-using-the-tfs-build-and-the-new-nuget-adapter-approach/)
 
-For Information on testing .Net core see  [Testing .NET Core with NUnit in Visual Studio 2017](https://www.alteridem.net/2017/05/04/test-net-core-nunit-vs2017/)
+For Information on testing .Net core see  [Testing .NET Core with NUnit in Visual Studio 2017](https://alteridem.net/2017/05/04/test-net-core-nunit-vs2017/)
 
 ## Reporting Problems
 

docs/articles/vs-test-adapter/Tips-And-Tricks.md

@@ -154,7 +154,7 @@ If you just need to add this, you can add a runsettings file (any filename, exte
 
 #### ShowInternalProperties
 
-The [NUnit internal properties](https://github.com/nunit/nunit/blob/master/src/NUnitFramework/framework/Internal/PropertyNames.cs) have been "over-populating" in the Test Explorer.  These are default filtered out, although you may still see these when you have [Source Based Discovery (SBD)](https://docs.microsoft.com/en-us/visualstudio/test/test-explorer-faq?view=vs-2017) turned on (which is the default in VS).  Once you have run test execution, they will be gone. We expect this part of the issue (SBD) to be fixed in VS.  If you still want to see them, set this property to true.
+The [NUnit internal properties](https://github.com/nunit/nunit/blob/master/src/NUnitFramework/framework/Internal/PropertyNames.cs) have been "over-populating" in the Test Explorer.  These are default filtered out, although you may still see these when you have [Source Based Discovery (SBD)](https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2017/test/test-explorer-faq?view=vs-2017) turned on (which is the default in VS).  Once you have run test execution, they will be gone. We expect this part of the issue (SBD) to be fixed in VS.  If you still want to see them, set this property to true.
 
 #### Where
 

docs/articles/vs-test-generator/Visual-Studio-Test-Generator.md

@@ -17,13 +17,13 @@ only have the `Create Unit Tests` menu option.
 
 You can download this extension in Visual Studio using **Tools | Extensions and Updates...**
 and searching for **Test Generator NUnit Extension**. You can also download from the
-[Visual Studio Gallery](https://visualstudiogallery.msdn.microsoft.com/bd30bf3f-4183-4b00-a245-1875316b8cd3) for VS 2015 and [here for VS 2017](https://marketplace.visualstudio.com/items?itemName=NUnitDevelopers.TestGeneratorNUnitextension-18371),
+[Visual Studio Gallery](https://marketplace.visualstudio.com/items?itemName=NUnitDevelopers.TestGeneratorNUnitextension) for VS 2015 and [here for VS 2017](https://marketplace.visualstudio.com/items?itemName=NUnitDevelopers.TestGeneratorNUnitextension-18371),
 or from the [GitHub Releases Page](https://github.com/nunit/nunit-vs-testgenerator/releases).
 
 ### How to Use
 
 For more information on using IntelliTest and this extension, please
-see the [Microsoft documentation](https://msdn.microsoft.com/en-us/library/dn823749.aspx).
+see the [Microsoft documentation](https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2015/test/generate-unit-tests-for-your-code-with-intellitest?view=vs-2015&redirectedfrom=MSDN).
 
 #### Right-Click to Create Tests