Add --self-contained and --no-self-contained options to dotnet test

[Copilot]

Plan: Add --self-contained and --no-self-contained options to dotnet test command

Implementation Checklist:

• Resolve merge conflict with main branch
• Add SelfContainedOption and NoSelfContainedOption to MicrosoftTestingPlatformOptions.cs (MTP only)
• Add options to ConfigureTestingPlatformCommand only (not VSTest)
• Validation in MicrosoftTestingPlatformTestCommand.cs only (not VSTest)
• Build and verify the changes work

Changes Made (Per Review Feedback):

Based on reviewer feedback that these options should be MTP-only, the implementation was updated:

1. MicrosoftTestingPlatformOptions.cs:

   • Added SelfContainedOption and NoSelfContainedOption properties

2. TestCommandDefinition.cs:

   • Removed SelfContainedOption and NoSelfContainedOption properties
   • Removed options from ConfigureVSTestCommand()
   • Updated ConfigureTestingPlatformCommand() to use MicrosoftTestingPlatformOptions.SelfContainedOption

3. TestCommand.cs (VSTest):

   • Removed validation for self-contained options (VSTest doesn't support these)

4. MicrosoftTestingPlatformTestCommand.cs:

   • Updated validation to reference MicrosoftTestingPlatformOptions.SelfContainedOption

5. Tests:

   • Removed VSTest-specific tests for these options since they're now MTP-only

Verification:

✅ Build succeeds in Debug configuration
✅ Options appear in dotnet test --help only when using MTP mode (via global.json)
✅ Options do NOT appear in VSTest mode

• Fixes Add '--self-contained' and '--no-self-contained' options to dotnet test command #31066

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add '--self-contained' and '--no-self-contained' options to dotnet test command</issue_title>
<issue_description>### Is your feature request related to a problem? Please describe.

Running:

dotnet test --configuration Release --runtime win-x86 --collect "XPlat Code Coverage"

Gives the following warning:

warning NETSDK1179: One of '--self-contained' or '--no-self-contained' options are required when '--runtime' is used.

However the dotnet test command does not support the --self-contained or --no-self-contained options.

Describe the solution you'd like

Add --self-contained and --no-self-contained option to dotnet test command.

Could be considered an alternate solution to #27151
</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Add '--self-contained' and '--no-self-contained' options to dotnet test command #31066

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Youssef1313]

Is the intent here to do that for MTP only? Or both MTP and VSTest?
I'm not sure if any of this will work well with VSTest. Looping @nohwnd in as well.

[marcpopMSFT]

@Youssef1313 any test type that supports exe tests should have these. I don't know if there is a way to filter the CLI like that so probably it should error if you use one of those flags with a test type that doesn't support that app type. The argument from Chet was that anything that does a build and builds an app should have these flag for consistency.

[Youssef1313]

In that case it is MTP only and is known at CLI level

[nohwnd]

I don't see this issue happening on net10.0 anymore, also noted by marc here: #27151 (comment)

Red because I don't have x86 runtime so tests cannot run, but no warning before:

Same for MTP, no warning:

[marcpopMSFT]

@copilot can you resolve the merge conflict

[marcpopMSFT]

@nohwnd for clarity, in triage we determined the other issue wasn't happening anymore but also Chet indicated that we should be consistent across our commands. Hence this PR (ie this is different than the intent of the original issue). Let me know if ya'll don't want these flags in dotnet test or there's a way to limit them to just MTP that I can tell copilot to do.

[Copilot]

@copilot can you resolve the merge conflict

Merge conflict resolved in commit 07ef2e5. The main branch had refactored TestCommandParser by moving all option definitions to a new TestCommandDefinition.cs file. I've adapted the changes to work with this new structure.

[marcpopMSFT]

@copilot resolve the conflicts

[Youssef1313]

The common option definition has the bug where it's a bool but the true/false value isn't considered right? Do we want to replicate this bug again in test command?

[marcpopMSFT]

Searching GH, I see around 15k instances of --self-contained true or --self-contained false

If we remove this, it'll break people but if we leave it, all of the false people will continue to be wrong.

Feels like we should break people or actually honor the bool. @baronfel ?

[marcpopMSFT]

@copilot try resolving the conflicts again