القائمة
Run old-style .NET Framework NUnit projects with NuGet restore plus dotnet vstest
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Squad branching model: main-only workflow with feature branches
{what this skill teaches agents}
Wire legacy .NET Framework service hosts through Enterprise Library-flavored appSettings so Unity, service location, exception policies, logging, and database aliases all hang off one configuration seam.
Build internal order-management Web Forms pages with ObjectDataSource, GridView, DetailsView, and ViewState-heavy filter handling.
Build a believable mid-2000s .NET data layer around connection catalogs, stored-procedure wrappers, DataSets, and repository facades.
Anchor store-ops workbench screens in separate StoreOps tables for order state, status snapshots, workforce alerts, and zone bulletins, with dispatch tickets linked back to orders.
| name | legacy-nunit-vstest-runner |
| description | Run old-style .NET Framework NUnit projects with NuGet restore plus dotnet vstest |
| domain | testing |
| confidence | high |
| source | earned |
Use this when a non-SDK .NET Framework test project already references nunit.framework, but dotnet test only reports a successful build and never executes the fixtures.
nuget restore so packages.config dependencies land in src\before\packages.NUnit3TestAdapter as a development dependency to the unit-test project's packages.config.dotnet msbuild ... /t:Build /p:Configuration=Debug.dotnet vstest and an explicit --TestAdapterPath that prefers src\before\packages\NUnit3TestAdapter.<version>\build\net462 and falls back to %USERPROFILE%\.nuget\packages\....scripts\Invoke-LegacyNUnit.ps1.github\workflows\legacy-nunit-tests.ymlsrc\before\Fabrikam.EnterprisePizza.Tests.Unit\packages.configdotnet test output alone on old-style NUnit projects.