You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Modern UWP net10 package builds but InvokeTestingPlatform cannot execute it #11601
A modern UWP test application using MSTest.Sdk, <UseUwp>true</UseUwp>, and <PublishAot>true</PublishAot> can build successfully when targeting net10.0-windows10.0.26100.0, but the Microsoft.Testing.Platform execution path cannot run the produced AppX recipe/executable through InvokeTestingPlatform.
The equivalent net9.0-windows10.0.26100.0 project builds and executes successfully through the MTP sidecar controller with package registration, AUMID activation, test discovery/execution, UI-thread tests, and TRX.
Observe that the .NET 10 package builds, but InvokeTestingPlatform rejects or cannot select the AppX recipe executable.
Change only the TFM to net9.0-windows10.0.26100.0; the same project executes successfully.
Expected behavior
Modern UWP tests targeting supported .NET 10 should execute through the same MTP sidecar-controller, package-registration, AUMID-activation, AppContainer IPC, UI dispatcher, and report pipeline as the validated .NET 9 configuration.
Actual behavior
The .NET 10 UWP package builds, but MTP execution cannot launch the AppX recipe executable. Users must currently keep the modern UWP test host on .NET 9 even when the rest of the solution targets .NET 10.
Additional context
Discovered while validating the public Windows application-model sample matrix for #11600. The proposed UwpMtpApp sample intentionally remains on net9.0-windows10.0.26100.0 and documents this release gate.
Please retain binlog-backed coverage for both the working net9 control and the net10 execution path when fixing this issue.
Activity