Add MAUI device deployment to dotnet test

[jonathanpeppers]

dotnet test can select MAUI devices, but unlike dotnet run it did not deploy the test application before computing its run arguments. This completes the device workflow so Microsoft.Testing.Platform test runs have equivalent build, deployment, and logging behavior.

• Selects devices before building so device-provided runtime identifiers participate in the build.
• Runs DeployToDevice before ComputeRunArguments for projects, solutions, and multi-targeted projects, including --no-build.
• Uses one command-owned MSBuild facade logger across framework selection, device selection, deployment, and run-argument computation.
• Reports deployment failures consistently, including parallel solution processing.
• Adds focused coverage for explicit and automatic selection, runtime identifiers, multi-targeting, solutions, failures, list-only behavior, and binlogs.
• Updates the MAUI command specification with the completed dotnet test pipeline.

Environment-variable propagation through -e is intentionally outside this change.

[Copilot]

Pull request overview

This PR completes the MAUI device workflow for dotnet test (Microsoft.Testing.Platform) by ensuring device selection happens early enough to influence the build, and by running DeployToDevice prior to ComputeRunArguments so test execution matches the dotnet run device pipeline more closely.

Changes:

• Select devices before building so device-provided runtime identifiers can participate in per-TFM builds.
• Invoke DeployToDevice (when present) before ComputeRunArguments, including for --no-build, solutions, and multi-targeted projects, with consistent error reporting in parallel solution processing.
• Add integration coverage around deployment behavior and binlog expectations; update the MAUI command spec accordingly.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
test/TestAssets/TestProjects/DotnetTestDevices/DotnetTestDevices.csproj	Adds DeployToDevice test target and ensures selected devices can provide a RID.
test/dotnet.Tests/CommandTests/Test/GivenDotnetTestSelectsDevice.cs	Expands integration tests to validate deploy ordering, failure behavior, and binlog content.
src/Cli/dotnet/Commands/Test/MTP/SolutionAndProjectUtility.cs	Adds logger plumbing and runs DeployToDevice before ComputeRunArguments when available.
src/Cli/dotnet/Commands/Test/MTP/MSBuildUtility.cs	Threads a command-owned logger through solution/project flows and improves graceful failure handling for parallel solution evaluation.
src/Cli/dotnet/Commands/Test/MTP/MSBuildHandler.cs	Passes the shared logger into MSBuild-based test initialization.
src/Cli/dotnet/Commands/Test/MTP/MicrosoftTestingPlatformTestCommand.cs	Owns a single binlog logger across selection/listing and MSBuild handler initialization, with deterministic shutdown.
documentation/specs/dotnet-run-for-maui.md	Documents the completed dotnet test device pipeline and binlog behavior.

[Evangelink]

Note

This review was generated with AI assistance and validated across multiple passes.

Overall this looks solid: the single command-owned FacadeLogger shut down once in finally matches the FacadeLogger/PersistentDispatcher multi-phase design, the unconditional DeployToDevice (when the target exists) mirrors dotnet run, RunCommandSelector explicitly does not own the passed logger, and the graceful-failure handling for parallel solution processing correctly avoids the AggregateException wrapping. Two low-confidence observations below.

[Evangelink]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

Merge conflicts are resolved in commit 8c32e76.

I merged origin/main into this branch and resolved the conflict in /src/Cli/dotnet/Commands/Test/MTP/SolutionAndProjectUtility.cs by keeping the MAUI deployment/run-arguments flow and also taking the new AOT suppression attribute from main.

[jonathanpeppers]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.