Skip to main content
Microsoft.Testing.Extensions.PackagedApp package icon

Microsoft.Testing.Extensions.PackagedApp

This package extends Microsoft Testing Platform to start Windows test hosts that cannot simply be Process.Started. In its Windows build (net*-windows) it registers a packaged MSIX app layout with the PackageManager and activates it by Application User Model ID, delivering platform arguments through argv for packagedClassicApp/win32App hosts or a reusable OnLaunched bootstrap for windowsApp/UWP hosts. When the selected application runs in AppContainer, the launcher also authorizes its exact package SID on the controller pipe with minimum client rights. A non-packaged (loose-layout) Windows test host can optionally be deployed to an isolated directory and launched from there. The launcher enables itself only for a packaged layout, so referencing it from an unpackaged app does not change how that app runs. These communication primitives do not change the current SDK/platform routing limitation: true UWP/AppContainer projects are still selected for VSTest rather than started as MTP test hosts. Microsoft Testing is a set of platform, framework and protocol intended to make it possible to run any test on any target or device.

Total Downloads
752
752
Published
Sep 16, 2026
Latest stable version

Install

.NET CLI
dotnet add package Microsoft.Testing.Extensions.PackagedApp --version 2.4.1
Package Manager Console
Install-Package Microsoft.Testing.Extensions.PackagedApp -Version 2.4.1
PackageReference
<PackageReference Include="Microsoft.Testing.Extensions.PackagedApp" Version="2.4.1" />

Frameworks

net8.0 net8.0-windows10.0.19041 net9.0 net9.0-windows10.0.19041

Dependencies

[2.4.1, 3.0.0)
Microsoft.Testing.Platform
net8.0-windows10.0.19041
[2.4.1, 3.0.0)
[2.4.1, 3.0.0)
Microsoft.Testing.Platform
net9.0-windows10.0.19041
[2.4.1, 3.0.0)

Adoption guide

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

Compatibility metadata lists 4 target frameworks; confirm the exact target used by your application.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.