[dotnet-run] implement "device" selection logic (#51914)

Context: https://github.com/dotnet/sdk/blob/5398e10de90dc9a27e0290ad55c2ae67360ea8be/documentation/specs/dotnet-run-for-maui.md

## Spec Changes ##

**Added RuntimeIdentifier Support**

- Examples to include `%(RuntimeIdentifier)` metadata (e.g., `android-arm64`, `ios-arm64`, `iossimulator-arm64`)

- When a device provides a `%(RuntimeIdentifier)`, it will be passed as `-p:RuntimeIdentifier` to subsequent MSBuild steps (build, deploy, ComputeRunArguments, run)

- `%(RuntimeIdentifier)` is optional but recommended

**Added Binary Logs Documentation**

- Added new section "Binary Logs for Device Selection" explaining:
  - When binlog files are created (when using `-bl:` with `dotnet run`)

## Implementation ##

**Renamed `TargetFrameworkSelector` to `RunCommandSelector`**

- Expanded scope from just framework selection to handle both target framework and device selection

- Made it a non-static class implementing `IDisposable` to:
  - Cache the MSBuild project instance across operations
  - Avoid loading/evaluating the project multiple times, except when global properties change
  - Properly manage MSBuild resources (ProjectCollection, Project, ProjectInstance) with `IDisposable`

- Added `InvalidateGlobalProperties()` method to re-evaluate the project when needed with a `$(TargetFramework)` global property change.

- Binary logger is owned by the `selector` instance and properly disposed.

**Added Tests**

- Mock test project (`DotnetRunDevices.csproj`) implements `ComputeAvailableDevices` target that returns hardcoded device items based on the target framework

- Test project includes `GenerateDeviceInfo` target that runs during build when a device is selected:
  - Generates `DeviceInfo.cs` with constants for `$(Device)` and `$(RuntimeIdentifier)` properties
  - Writes to intermediate output directory before compilation

- Test application prints these generated constants, allowing tests to verify that:
  - The correct device ID was passed to MSBuild
  - `$(RuntimeIdentifier)` was propagated correctly (when provided by device)
  - Multi-targeted apps can have different devices per framework

Author: jonathanpeppers

documentation/specs/dotnet-run-for-maui.md

@@ -56,21 +56,24 @@ to make extensible for .NET MAUI (and future) scenarios.
 ```xml
 <ItemGroup>
   <!-- Android examples -->
-  <Devices Include="emulator-5554"  Description="Pixel 7 - API 35" Type="Emulator" Status="Offline" />
-  <Devices Include="emulator-5555"  Description="Pixel 7 - API 36" Type="Emulator" Status="Online" />
-  <Devices Include="0A041FDD400327" Description="Pixel 7 Pro"      Type="Device"   Status="Online" />
+  <Devices Include="emulator-5554"  Description="Pixel 7 - API 35" Type="Emulator" Status="Offline" RuntimeIdentifier="android-x64" />
+  <Devices Include="emulator-5555"  Description="Pixel 7 - API 36" Type="Emulator" Status="Online"  RuntimeIdentifier="android-x64" />
+  <Devices Include="0A041FDD400327" Description="Pixel 7 Pro"      Type="Device"   Status="Online"  RuntimeIdentifier="android-arm64" />
   <!-- iOS examples -->
-  <Devices Include="94E71AE5-8040-4DB2-8A9C-6CD24EF4E7DE" Description="iPhone 11 - iOS 18.6" Type="Simulator" Status="Shutdown" />
-  <Devices Include="FBF5DCE8-EE2B-4215-8118-3A2190DE1AD7" Description="iPhone 14 - iOS 26.0" Type="Simulator" Status="Booted" />
-  <Devices Include="23261B78-1E31-469C-A46E-1776D386EFD8" Description="My iPhone 13"         Type="Device"    Status="Unavailable" />
-  <Devices Include="AF40CC64-2CDB-5F16-9651-86BCDF380881" Description="My iPhone 15"         Type="Device"    Status="Paired" />
+  <Devices Include="94E71AE5-8040-4DB2-8A9C-6CD24EF4E7DE" Description="iPhone 11 - iOS 18.6" Type="Simulator" Status="Shutdown"    RuntimeIdentifier="iossimulator-arm64" />
+  <Devices Include="FBF5DCE8-EE2B-4215-8118-3A2190DE1AD7" Description="iPhone 14 - iOS 26.0" Type="Simulator" Status="Booted"      RuntimeIdentifier="iossimulator-arm64" />
+  <Devices Include="23261B78-1E31-469C-A46E-1776D386EFD8" Description="My iPhone 13"         Type="Device"    Status="Unavailable" RuntimeIdentifier="ios-arm64" />
+  <Devices Include="AF40CC64-2CDB-5F16-9651-86BCDF380881" Description="My iPhone 15"         Type="Device"    Status="Paired"      RuntimeIdentifier="ios-arm64" />
 </ItemGroup>
 ```
 
-_NOTE: each workload can decide which metadata values for `%(Type)`
-and `%(Status)` are useful, filtering offline devices, etc. The output
-above would be analogous to running `adb devices`, `xcrun simctl list
-devices`, or `xcrun devicectl list devices`._
+_NOTE: each workload can decide which metadata values for `%(Type)`,
+`%(Status)`, and `%(RuntimeIdentifier)` are useful, filtering offline
+devices, etc. The output above would be analogous to running `adb
+devices`, `xcrun simctl list devices`, or `xcrun devicectl list
+devices`. The `%(RuntimeIdentifier)` metadata is optional but
+recommended, as it allows the build system to pass the appropriate RID
+to subsequent build, deploy, and run steps._
 
 * Continuing on...
 
@@ -81,24 +84,28 @@ devices`, or `xcrun devicectl list devices`._
     `--device` switch. Listing the options returned by the
     `ComputeAvailableDevices` MSBuild target.
 
-* `build`: unchanged, but is passed `-p:Device`.
+* `build`: unchanged, but is passed `-p:Device` and optionally `-p:RuntimeIdentifier`
+  if the selected device provided a `%(RuntimeIdentifier)` metadata value.
 
 * `deploy`
 
   * If a `DeployToDevice` MSBuild target is available, provided by the
     iOS or Android workload, etc.
 
   * Call the MSBuild target, passing in the identifier for the selected
-    `-p:Device` global MSBuild property.
+    `-p:Device` global MSBuild property, and optionally `-p:RuntimeIdentifier`
+    if the selected device provided a `%(RuntimeIdentifier)` metadata value.
 
   * This step needs to run, even with `--no-build`, as you may have
     selected a different device.
 
-* `ComputeRunArguments`: unchanged, but is passed `-p:Device`.
+* `ComputeRunArguments`: unchanged, but is passed `-p:Device` and optionally
+  `-p:RuntimeIdentifier` if the selected device provided a `%(RuntimeIdentifier)` 
+  metadata value.
 
 * `run`: unchanged. `ComputeRunArguments` should have set a valid
   `$(RunCommand)` and `$(RunArguments)` using the value supplied by
-  `-p:Device`.
+  `-p:Device` and optionally `-p:RuntimeIdentifier`.
 
 ## New `dotnet run` Command-line Switches
 
@@ -139,6 +146,20 @@ A new `--device` switch will:
 * The iOS and Android workloads will know how to interpret `$(Device)`
   to select an appropriate device, emulator, or simulator.
 
+## Binary Logs for Device Selection
+
+When using `-bl` with `dotnet run`, all MSBuild operations are logged to a single
+binlog file: device selection, build, deploy, and run argument computation.
+
+File naming for `dotnet run` binlogs:
+
+* `-bl:filename.binlog` creates `filename-dotnet-run.binlog`
+* `-bl` creates `msbuild-dotnet-run.binlog`
+
+Note: The build step may also create `msbuild.binlog` separately. Use
+`--no-build` with `-bl` to only capture run-specific MSBuild
+operations.
+
 ## What about Launch Profiles?
 
 The iOS and Android workloads ignore all

src/Cli/Microsoft.DotNet.Cli.Utils/Constants.cs

@@ -29,6 +29,7 @@ public static class Constants
     // MSBuild targets
     public const string Build = nameof(Build);
     public const string ComputeRunArguments = nameof(ComputeRunArguments);
+    public const string ComputeAvailableDevices = nameof(ComputeAvailableDevices);
     public const string CoreCompile = nameof(CoreCompile);
 
     // MSBuild item metadata

src/Cli/dotnet/Commands/CliCommandStrings.resx

@@ -1786,6 +1786,30 @@ Your project targets multiple frameworks. Specify which framework to run using '
   <data name="RunRuntimeOptionDescription" xml:space="preserve">
     <value>The target runtime to run for.</value>
   </data>
+  <data name="CommandOptionDeviceDescription" xml:space="preserve">
+    <value>The device identifier to use for running the application.</value>
+  </data>
+  <data name="CommandOptionDeviceHelpName" xml:space="preserve">
+    <value>DEVICE</value>
+  </data>
+  <data name="CommandOptionListDevicesDescription" xml:space="preserve">
+    <value>List available devices for running the application.</value>
+  </data>
+  <data name="RunCommandAvailableDevices" xml:space="preserve">
+    <value>Available devices:</value>
+  </data>
+  <data name="RunCommandNoDevicesAvailable" xml:space="preserve">
+    <value>No devices are available for this project.</value>
+  </data>
+  <data name="RunCommandSelectDevicePrompt" xml:space="preserve">
+    <value>Select a device to run on:</value>
+  </data>
+  <data name="RunCommandMoreDevicesText" xml:space="preserve">
+    <value>Move up and down to reveal more devices</value>
+  </data>
+  <data name="RunCommandExceptionUnableToRunSpecifyDevice" xml:space="preserve">
+    <value>Unable to run this project because multiple devices are available. Please specify which device to use by passing the {0} argument with one of the following values:</value>
+  </data>
   <data name="RuntimeConfigDefinition" xml:space="preserve">
     <value>Path to &lt;application&gt;.runtimeconfig.json file.</value>
   </data>

src/Cli/dotnet/Commands/Run/Api/RunApiCommand.cs

@@ -102,6 +102,8 @@ public override RunApiOutput Execute()
                 launchProfile: null,
                 noLaunchProfile: false,
                 noLaunchProfileArguments: false,
+                device: null,
+                listDevices: false,
                 noRestore: false,
                 noCache: false,
                 interactive: false,
@@ -112,7 +114,7 @@ public override RunApiOutput Execute()
                 msbuildRestoreProperties: ReadOnlyDictionary<string, string>.Empty);
 
             runCommand.TryGetLaunchProfileSettingsIfNeeded(out var launchSettings);
-            var targetCommand = (Utils.Command)runCommand.GetTargetCommand(buildCommand.CreateProjectInstance, cachedRunProperties: null);
+            var targetCommand = (Utils.Command)runCommand.GetTargetCommand(buildCommand.CreateProjectInstance, cachedRunProperties: null, logger: null);
             runCommand.ApplyLaunchSettingsProfileToCommand(targetCommand, launchSettings);
 
             return new RunApiOutput.RunCommand