Run single test using docker image

[verdie-g]

In docs/workflow/testing/libraries/testing.md it states that dotnet build should be used to run a single library/test but it doesn't seem to be available in the docker image. Is this scenario supported by the docker image?

[vcsjones]

If you mean run a single library in a Codespace, use dotnet.sh instead of dotnet.

Like dotnet.sh build /t:Test /p:XUnitOptions="-class Test.ClassUnderTests"

[verdie-g]

Oh thanks. Would it make sense to replace dotnet with dotnet.sh in the doc or most devs use the former?

[ghost]

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

Issue Details

---

In docs/workflow/testing/libraries/testing.md it states that dotnet build should be used to run a single library/test but it doesn't seem to be available in the docker image. Is this scenario supported by the docker image?

Author:	verdie-g
Assignees:	-
Labels:	area-Infrastructure-libraries, untriaged
Milestone:	-

[ViktorHofer]

dotnet works well if it's installed globally on the machine. Right now that should be case for most devs as we depend on the stable 8.0.100 SDK. We encourage devs to install the required SDK on their machines for optimal tooling support, i.e. VS and VSCode.

dotnet.sh either uses the globally installed SDK (if the version matches) or downloads the SDK and puts it into the repository under the .dotnet folder (repo local SDK).

[verdie-g]

What do you think of such change in the doc #95557 ?

[huoyaoyuan]

.\dotnet.cmd and ./dotnet.sh are both used for local dotnet SDK resolving. I don't think it's specified to docker.

Will global dotnet run successfully when the repo is using a nightly SDK?

[verdie-g]

So what are the recommendations dotnet.sh VS global dotnet?

cc @ViktorHofer

[ViktorHofer]

If the machine doesn't have the required (specified in the repo's global.json) SDK installed, use dotnet.cmd/sh, otherwise just use the dotnet on the path.