From c192a031fbc459f8c005450de1a43517796d9635 Mon Sep 17 00:00:00 2001 From: Sean Killeen Date: Thu, 22 Oct 2026 08:34:13 -0400 Subject: [PATCH] Fix outdated NUnitLite Program.cs text on the installation page The NUnitLite section of the installation page still said the package adds a `Program.cs` and therefore can't be combined with an ordinary test project. The package hasn't shipped a `Program.cs` for years, and the NUnitLite page already explains that you write `Main` yourself. Replaces the paragraph with an accurate description that points to the NUnitLite page. Fixes #665 Co-Authored-By: Claude Fable 5.1 --- docs/articles/nunit/getting-started/installation.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/articles/nunit/getting-started/installation.md b/docs/articles/nunit/getting-started/installation.md index 1b4a45149..44efcb5fd 100644 --- a/docs/articles/nunit/getting-started/installation.md +++ b/docs/articles/nunit/getting-started/installation.md @@ -166,8 +166,10 @@ to add a reference to the `NUnitLite` package in your test assembly. To run your tests, simply run your executable test assembly. No other runner is needed. -Note that since this approach includes a `Program.cs` it can not be combined with the ordinary unit test project, as -that would create two entry points, which would confuse the compiler. +The package does not add a `Program.cs` to your project. You write the `Main` method yourself and call the NUnitLite +runner from it, as shown on the [NUnitLite](xref:nunitlite) page. Because the test project becomes a console +application with its own entry point, you can run the tests with `dotnet run` as well as with `dotnet test` or the +Visual Studio Test Explorer. ### Downloading the Zip File -- Not Recommended