Downloading NUnit

[OsirisTerje]

Added detailed instructions on how to download NUnit, including developer versions.

For those that need the little extra.

Fixes#1206

[Copilot]

Pull request overview

This PR adds a new “Downloading” page under NUnit’s Getting Started docs to provide explicit instructions for obtaining both release and developer (alpha) packages.

Changes:

• Added a new “Downloading” documentation page with instructions and NuGet/MyGet configuration examples.
• Linked the new page into the Getting Started TOC.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
docs/articles/nunit/getting-started/toc.yml	Adds a “Downloading” entry to the Getting Started navigation.
docs/articles/nunit/getting-started/downloading.md	New page documenting where to download release and developer (alpha) NUnit packages and how to configure feeds.

Suppressed comments (4)

docs/articles/nunit/getting-started/downloading.md:23

• “GitHub” should be capitalized consistently, and this reads better if you use the standard “Releases” wording and plural “discussions”.

You can also find the release package at the [Release section](https://github.com/nunit/nunit/releases) in
our [github repo](https://github.com/nunit/nunit).
The repo is also where you can raise issues, download code, join discussion or just look around.

docs/articles/nunit/getting-started/downloading.md:27

• The Markdown link on this line is malformed (extra ] / mismatched parentheses), which will break rendering. If the intent is a MyGet pre-release badge linking to the feed, format it as an image link and use the “MyGet” casing.

We also release developer versions, they are called `alpha` versions, and you find them at our place at [Myget](https://img.shields.io/myget/nunit/vpre/NUnit.svg?label=MyGet%3A%20Latest%20pre-release&style=flat)](<https://www.myget.org/feed/nunit/package/nuget/NUnit>).

docs/articles/nunit/getting-started/downloading.md:33

• Avoid the trailing double-spaces at end-of-line (MD009-style lint), and fix the missing apostrophe in “don't”. Also consider consistent “MyGet” casing.

The easiest way to get the developer versions, is to add it to your nuget.config file, or if you dont have it, just create one. The code snippet below is the full content of a nuget.config file which includes the Myget feed.

docs/articles/nunit/getting-started/downloading.md:45

• This paragraph has a double space after the period and some awkward phrasing (“if you like to use it over time”). Tightening the wording improves readability.

Note that if you use [Central Package Management](https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management) you will get a [NU1507](https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1507) warning about having two feeds and not having [package source mapping](https://learn.microsoft.com/en-us/nuget/consume-packages/package-source-mapping). You can just ignore this warning if you're just going to test it, but if you like to use it over time, you should add it like shown below.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[OsirisTerje]

Added detailed instructions on how to download NUnit, including developer versions.

For those that need the little extra.

Fixes#1206

[Copilot]

Pull request overview

This PR adds a new “Downloading” page under NUnit’s Getting Started docs to provide explicit instructions for obtaining both release and developer (alpha) packages.

Changes:

• Added a new “Downloading” documentation page with instructions and NuGet/MyGet configuration examples.
• Linked the new page into the Getting Started TOC.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
docs/articles/nunit/getting-started/toc.yml	Adds a “Downloading” entry to the Getting Started navigation.
docs/articles/nunit/getting-started/downloading.md	New page documenting where to download release and developer (alpha) NUnit packages and how to configure feeds.

Suppressed comments (4)

docs/articles/nunit/getting-started/downloading.md:23

• “GitHub” should be capitalized consistently, and this reads better if you use the standard “Releases” wording and plural “discussions”.

You can also find the release package at the [Release section](https://github.com/nunit/nunit/releases) in
our [github repo](https://github.com/nunit/nunit).
The repo is also where you can raise issues, download code, join discussion or just look around.

docs/articles/nunit/getting-started/downloading.md:27

• The Markdown link on this line is malformed (extra ] / mismatched parentheses), which will break rendering. If the intent is a MyGet pre-release badge linking to the feed, format it as an image link and use the “MyGet” casing.

We also release developer versions, they are called `alpha` versions, and you find them at our place at [Myget](https://img.shields.io/myget/nunit/vpre/NUnit.svg?label=MyGet%3A%20Latest%20pre-release&style=flat)](<https://www.myget.org/feed/nunit/package/nuget/NUnit>).

docs/articles/nunit/getting-started/downloading.md:33

• Avoid the trailing double-spaces at end-of-line (MD009-style lint), and fix the missing apostrophe in “don't”. Also consider consistent “MyGet” casing.

The easiest way to get the developer versions, is to add it to your nuget.config file, or if you dont have it, just create one. The code snippet below is the full content of a nuget.config file which includes the Myget feed.

docs/articles/nunit/getting-started/downloading.md:45

• This paragraph has a double space after the period and some awkward phrasing (“if you like to use it over time”). Tightening the wording improves readability.

Note that if you use [Central Package Management](https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management) you will get a [NU1507](https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1507) warning about having two feeds and not having [package source mapping](https://learn.microsoft.com/en-us/nuget/consume-packages/package-source-mapping). You can just ignore this warning if you're just going to test it, but if you like to use it over time, you should add it like shown below.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[OsirisTerje]

Added detailed instructions on how to download NUnit, including developer versions.

For those that need the little extra.

Fixes#1206

[Copilot]

Pull request overview

This PR adds a new “Downloading” page under NUnit’s Getting Started docs to provide explicit instructions for obtaining both release and developer (alpha) packages.

Changes:

• Added a new “Downloading” documentation page with instructions and NuGet/MyGet configuration examples.
• Linked the new page into the Getting Started TOC.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
docs/articles/nunit/getting-started/toc.yml	Adds a “Downloading” entry to the Getting Started navigation.
docs/articles/nunit/getting-started/downloading.md	New page documenting where to download release and developer (alpha) NUnit packages and how to configure feeds.

Suppressed comments (4)

docs/articles/nunit/getting-started/downloading.md:23

• “GitHub” should be capitalized consistently, and this reads better if you use the standard “Releases” wording and plural “discussions”.

You can also find the release package at the [Release section](https://github.com/nunit/nunit/releases) in
our [github repo](https://github.com/nunit/nunit).
The repo is also where you can raise issues, download code, join discussion or just look around.

docs/articles/nunit/getting-started/downloading.md:27

• The Markdown link on this line is malformed (extra ] / mismatched parentheses), which will break rendering. If the intent is a MyGet pre-release badge linking to the feed, format it as an image link and use the “MyGet” casing.

We also release developer versions, they are called `alpha` versions, and you find them at our place at [Myget](https://img.shields.io/myget/nunit/vpre/NUnit.svg?label=MyGet%3A%20Latest%20pre-release&style=flat)](<https://www.myget.org/feed/nunit/package/nuget/NUnit>).

docs/articles/nunit/getting-started/downloading.md:33

• Avoid the trailing double-spaces at end-of-line (MD009-style lint), and fix the missing apostrophe in “don't”. Also consider consistent “MyGet” casing.

The easiest way to get the developer versions, is to add it to your nuget.config file, or if you dont have it, just create one. The code snippet below is the full content of a nuget.config file which includes the Myget feed.

docs/articles/nunit/getting-started/downloading.md:45

• This paragraph has a double space after the period and some awkward phrasing (“if you like to use it over time”). Tightening the wording improves readability.

Note that if you use [Central Package Management](https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management) you will get a [NU1507](https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1507) warning about having two feeds and not having [package source mapping](https://learn.microsoft.com/en-us/nuget/consume-packages/package-source-mapping). You can just ignore this warning if you're just going to test it, but if you like to use it over time, you should add it like shown below.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[OsirisTerje]

Added detailed instructions on how to download NUnit, including developer versions.

For those that need the little extra.

Fixes#1206

[Copilot]

Pull request overview

This PR adds a new “Downloading” page under NUnit’s Getting Started docs to provide explicit instructions for obtaining both release and developer (alpha) packages.

Changes:

• Added a new “Downloading” documentation page with instructions and NuGet/MyGet configuration examples.
• Linked the new page into the Getting Started TOC.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
docs/articles/nunit/getting-started/toc.yml	Adds a “Downloading” entry to the Getting Started navigation.
docs/articles/nunit/getting-started/downloading.md	New page documenting where to download release and developer (alpha) NUnit packages and how to configure feeds.

Suppressed comments (4)

docs/articles/nunit/getting-started/downloading.md:23

• “GitHub” should be capitalized consistently, and this reads better if you use the standard “Releases” wording and plural “discussions”.

You can also find the release package at the [Release section](https://github.com/nunit/nunit/releases) in
our [github repo](https://github.com/nunit/nunit).
The repo is also where you can raise issues, download code, join discussion or just look around.

docs/articles/nunit/getting-started/downloading.md:27

• The Markdown link on this line is malformed (extra ] / mismatched parentheses), which will break rendering. If the intent is a MyGet pre-release badge linking to the feed, format it as an image link and use the “MyGet” casing.

We also release developer versions, they are called `alpha` versions, and you find them at our place at [Myget](https://img.shields.io/myget/nunit/vpre/NUnit.svg?label=MyGet%3A%20Latest%20pre-release&style=flat)](<https://www.myget.org/feed/nunit/package/nuget/NUnit>).

docs/articles/nunit/getting-started/downloading.md:33

• Avoid the trailing double-spaces at end-of-line (MD009-style lint), and fix the missing apostrophe in “don't”. Also consider consistent “MyGet” casing.

The easiest way to get the developer versions, is to add it to your nuget.config file, or if you dont have it, just create one. The code snippet below is the full content of a nuget.config file which includes the Myget feed.

docs/articles/nunit/getting-started/downloading.md:45

• This paragraph has a double space after the period and some awkward phrasing (“if you like to use it over time”). Tightening the wording improves readability.

Note that if you use [Central Package Management](https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management) you will get a [NU1507](https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1507) warning about having two feeds and not having [package source mapping](https://learn.microsoft.com/en-us/nuget/consume-packages/package-source-mapping). You can just ignore this warning if you're just going to test it, but if you like to use it over time, you should add it like shown below.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[OsirisTerje]

Added detailed instructions on how to download NUnit, including developer versions.

For those that need the little extra.

Fixes#1206

[Copilot]

Pull request overview

This PR adds a new “Downloading” page under NUnit’s Getting Started docs to provide explicit instructions for obtaining both release and developer (alpha) packages.

Changes:

• Added a new “Downloading” documentation page with instructions and NuGet/MyGet configuration examples.
• Linked the new page into the Getting Started TOC.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
docs/articles/nunit/getting-started/toc.yml	Adds a “Downloading” entry to the Getting Started navigation.
docs/articles/nunit/getting-started/downloading.md	New page documenting where to download release and developer (alpha) NUnit packages and how to configure feeds.

Suppressed comments (4)

docs/articles/nunit/getting-started/downloading.md:23

• “GitHub” should be capitalized consistently, and this reads better if you use the standard “Releases” wording and plural “discussions”.

You can also find the release package at the [Release section](https://github.com/nunit/nunit/releases) in
our [github repo](https://github.com/nunit/nunit).
The repo is also where you can raise issues, download code, join discussion or just look around.

docs/articles/nunit/getting-started/downloading.md:27

• The Markdown link on this line is malformed (extra ] / mismatched parentheses), which will break rendering. If the intent is a MyGet pre-release badge linking to the feed, format it as an image link and use the “MyGet” casing.

We also release developer versions, they are called `alpha` versions, and you find them at our place at [Myget](https://img.shields.io/myget/nunit/vpre/NUnit.svg?label=MyGet%3A%20Latest%20pre-release&style=flat)](<https://www.myget.org/feed/nunit/package/nuget/NUnit>).

docs/articles/nunit/getting-started/downloading.md:33

• Avoid the trailing double-spaces at end-of-line (MD009-style lint), and fix the missing apostrophe in “don't”. Also consider consistent “MyGet” casing.

The easiest way to get the developer versions, is to add it to your nuget.config file, or if you dont have it, just create one. The code snippet below is the full content of a nuget.config file which includes the Myget feed.

docs/articles/nunit/getting-started/downloading.md:45

• This paragraph has a double space after the period and some awkward phrasing (“if you like to use it over time”). Tightening the wording improves readability.

Note that if you use [Central Package Management](https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management) you will get a [NU1507](https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1507) warning about having two feeds and not having [package source mapping](https://learn.microsoft.com/en-us/nuget/consume-packages/package-source-mapping). You can just ignore this warning if you're just going to test it, but if you like to use it over time, you should add it like shown below.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[OsirisTerje]

Added detailed instructions on how to download NUnit, including developer versions.

For those that need the little extra.

Fixes#1206

[Copilot]

Pull request overview

This PR adds a new “Downloading” page under NUnit’s Getting Started docs to provide explicit instructions for obtaining both release and developer (alpha) packages.

Changes:

• Added a new “Downloading” documentation page with instructions and NuGet/MyGet configuration examples.
• Linked the new page into the Getting Started TOC.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
docs/articles/nunit/getting-started/toc.yml	Adds a “Downloading” entry to the Getting Started navigation.
docs/articles/nunit/getting-started/downloading.md	New page documenting where to download release and developer (alpha) NUnit packages and how to configure feeds.

Suppressed comments (4)

docs/articles/nunit/getting-started/downloading.md:23

• “GitHub” should be capitalized consistently, and this reads better if you use the standard “Releases” wording and plural “discussions”.

You can also find the release package at the [Release section](https://github.com/nunit/nunit/releases) in
our [github repo](https://github.com/nunit/nunit).
The repo is also where you can raise issues, download code, join discussion or just look around.

docs/articles/nunit/getting-started/downloading.md:27

• The Markdown link on this line is malformed (extra ] / mismatched parentheses), which will break rendering. If the intent is a MyGet pre-release badge linking to the feed, format it as an image link and use the “MyGet” casing.

We also release developer versions, they are called `alpha` versions, and you find them at our place at [Myget](https://img.shields.io/myget/nunit/vpre/NUnit.svg?label=MyGet%3A%20Latest%20pre-release&style=flat)](<https://www.myget.org/feed/nunit/package/nuget/NUnit>).

docs/articles/nunit/getting-started/downloading.md:33

• Avoid the trailing double-spaces at end-of-line (MD009-style lint), and fix the missing apostrophe in “don't”. Also consider consistent “MyGet” casing.

The easiest way to get the developer versions, is to add it to your nuget.config file, or if you dont have it, just create one. The code snippet below is the full content of a nuget.config file which includes the Myget feed.

docs/articles/nunit/getting-started/downloading.md:45

• This paragraph has a double space after the period and some awkward phrasing (“if you like to use it over time”). Tightening the wording improves readability.

Note that if you use [Central Package Management](https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management) you will get a [NU1507](https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1507) warning about having two feeds and not having [package source mapping](https://learn.microsoft.com/en-us/nuget/consume-packages/package-source-mapping). You can just ignore this warning if you're just going to test it, but if you like to use it over time, you should add it like shown below.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[OsirisTerje]

Added detailed instructions on how to download NUnit, including developer versions.

For those that need the little extra.

Fixes#1206

[Copilot]

Pull request overview

This PR adds a new “Downloading” page under NUnit’s Getting Started docs to provide explicit instructions for obtaining both release and developer (alpha) packages.

Changes:

• Added a new “Downloading” documentation page with instructions and NuGet/MyGet configuration examples.
• Linked the new page into the Getting Started TOC.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
docs/articles/nunit/getting-started/toc.yml	Adds a “Downloading” entry to the Getting Started navigation.
docs/articles/nunit/getting-started/downloading.md	New page documenting where to download release and developer (alpha) NUnit packages and how to configure feeds.

Suppressed comments (4)

docs/articles/nunit/getting-started/downloading.md:23

• “GitHub” should be capitalized consistently, and this reads better if you use the standard “Releases” wording and plural “discussions”.

You can also find the release package at the [Release section](https://github.com/nunit/nunit/releases) in
our [github repo](https://github.com/nunit/nunit).
The repo is also where you can raise issues, download code, join discussion or just look around.

docs/articles/nunit/getting-started/downloading.md:27

• The Markdown link on this line is malformed (extra ] / mismatched parentheses), which will break rendering. If the intent is a MyGet pre-release badge linking to the feed, format it as an image link and use the “MyGet” casing.

We also release developer versions, they are called `alpha` versions, and you find them at our place at [Myget](https://img.shields.io/myget/nunit/vpre/NUnit.svg?label=MyGet%3A%20Latest%20pre-release&style=flat)](<https://www.myget.org/feed/nunit/package/nuget/NUnit>).

docs/articles/nunit/getting-started/downloading.md:33

• Avoid the trailing double-spaces at end-of-line (MD009-style lint), and fix the missing apostrophe in “don't”. Also consider consistent “MyGet” casing.

The easiest way to get the developer versions, is to add it to your nuget.config file, or if you dont have it, just create one. The code snippet below is the full content of a nuget.config file which includes the Myget feed.

docs/articles/nunit/getting-started/downloading.md:45

• This paragraph has a double space after the period and some awkward phrasing (“if you like to use it over time”). Tightening the wording improves readability.

Note that if you use [Central Package Management](https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management) you will get a [NU1507](https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1507) warning about having two feeds and not having [package source mapping](https://learn.microsoft.com/en-us/nuget/consume-packages/package-source-mapping). You can just ignore this warning if you're just going to test it, but if you like to use it over time, you should add it like shown below.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[OsirisTerje]

Added detailed instructions on how to download NUnit, including developer versions.

For those that need the little extra.

Fixes#1206

[Copilot]

Pull request overview

This PR adds a new “Downloading” page under NUnit’s Getting Started docs to provide explicit instructions for obtaining both release and developer (alpha) packages.

Changes:

• Added a new “Downloading” documentation page with instructions and NuGet/MyGet configuration examples.
• Linked the new page into the Getting Started TOC.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
docs/articles/nunit/getting-started/toc.yml	Adds a “Downloading” entry to the Getting Started navigation.
docs/articles/nunit/getting-started/downloading.md	New page documenting where to download release and developer (alpha) NUnit packages and how to configure feeds.

Suppressed comments (4)

docs/articles/nunit/getting-started/downloading.md:23

• “GitHub” should be capitalized consistently, and this reads better if you use the standard “Releases” wording and plural “discussions”.

You can also find the release package at the [Release section](https://github.com/nunit/nunit/releases) in
our [github repo](https://github.com/nunit/nunit).
The repo is also where you can raise issues, download code, join discussion or just look around.

docs/articles/nunit/getting-started/downloading.md:27

• The Markdown link on this line is malformed (extra ] / mismatched parentheses), which will break rendering. If the intent is a MyGet pre-release badge linking to the feed, format it as an image link and use the “MyGet” casing.

We also release developer versions, they are called `alpha` versions, and you find them at our place at [Myget](https://img.shields.io/myget/nunit/vpre/NUnit.svg?label=MyGet%3A%20Latest%20pre-release&style=flat)](<https://www.myget.org/feed/nunit/package/nuget/NUnit>).

docs/articles/nunit/getting-started/downloading.md:33

• Avoid the trailing double-spaces at end-of-line (MD009-style lint), and fix the missing apostrophe in “don't”. Also consider consistent “MyGet” casing.

The easiest way to get the developer versions, is to add it to your nuget.config file, or if you dont have it, just create one. The code snippet below is the full content of a nuget.config file which includes the Myget feed.

docs/articles/nunit/getting-started/downloading.md:45

• This paragraph has a double space after the period and some awkward phrasing (“if you like to use it over time”). Tightening the wording improves readability.

Note that if you use [Central Package Management](https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management) you will get a [NU1507](https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1507) warning about having two feeds and not having [package source mapping](https://learn.microsoft.com/en-us/nuget/consume-packages/package-source-mapping). You can just ignore this warning if you're just going to test it, but if you like to use it over time, you should add it like shown below.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.