Using winapp CLI with .NET

This guide should work for most .NET project types. The steps have been tested with both console and UI-based projects like WPF. For working examples, check out the dotnet-app (console) and wpf-app (WPF) samples in the samples folder.

This guide demonstrates how to use the winapp CLI with a .NET application to debug with package identity and package your application as an MSIX.

Package identity is a core concept in the Windows app model. It allows your application to access specific Windows APIs (like Notifications, Security, AI APIs, etc), have a clean install/uninstall experience, and more.

A standard executable (like one created with dotnet build) does not have package identity. This guide shows how to add it for debugging and then package it for distribution.

Prerequisites

.NET SDK: Install the .NET SDK (requires a restart after installation):
```
winget install Microsoft.DotNet.SDK.10 --source winget
```
winapp CLI: Install the winapp tool via winget (or update if already installed):
```
winget install Microsoft.winappcli --source winget
```

1. Create a New .NET App

Start by creating a simple .NET console application:

dotnet new console -n dotnet-app
cd dotnet-app

Run it to make sure everything is working:

dotnet run

Output should be "Hello, World!"

2. Update Code to Check Identity

We'll update the app to check if it's running with package identity. We'll use the Windows Runtime API to access the Package APIs.

First, update your project file to target a specific Windows SDK version. Open dotnet-app.csproj and change the TargetFramework to include the Windows SDK version:

  <TargetFramework>net10.0-windows10.0.26100.0</TargetFramework>

This gives you access to Windows Runtime APIs without needing additional packages.

Now replace the contents of Program.cs with the following code. This code attempts to retrieve the current package identity using the Windows Runtime API. If it succeeds, it prints the Package Family Name; otherwise, it prints "Not packaged".

using Windows.ApplicationModel;

try
{
    var package = Package.Current;
    var familyName = package.Id.FamilyName;
    Console.WriteLine($"Package Family Name: {familyName}");
}
catch (InvalidOperationException)
{
    // Thrown when app doesn't have package identity
    Console.WriteLine("Not packaged");
}

3. Run Without Identity

Now, run the app as usual:

dotnet run

You should see the output "Not packaged". This confirms that the standard executable is running without any package identity.

4. Initialize Project with winapp CLI

The winapp init command automatically detects .csproj files and runs a .NET-specific setup. It sets up everything you need in one go: validates your TargetFramework, adds required NuGet packages, generates the app manifest, and assets.

Run the following command and follow the prompts:

winapp init

When prompted:

Package name: Press Enter to accept the default (dotnet-app)
Publisher name: Press Enter to accept the default or enter your name
Version: Press Enter to accept 1.0.0.0
Description: Press Enter to accept the default (Windows Application) or enter a description
Windows App SDK setup: Select Stable, Preview, or Experimental (determines which Windows App SDK version is added)
TargetFramework update: If your TargetFramework doesn't include a supported Windows SDK version, you'll be prompted to update it (e.g., to net10.0-windows10.0.26100.0)
Developer Mode: If you are prompted about "Developer Mode", you can turn it on if you would like, but be aware that it requires administrative privileges

This command will:

Update the TargetFramework in your .csproj to a supported Windows TFM (if needed)
Add Microsoft.WindowsAppSDK, Microsoft.Windows.SDK.BuildTools, and Microsoft.Windows.SDK.BuildTools.WinApp NuGet package references to your .csproj
Create Package.appxmanifest and Assets folder for your app identity

Note

Unlike native/C++ projects, the .NET flow does not create a winapp.yaml file. NuGet packages are managed directly via your .csproj. After cloning, run winapp restore or dotnet restore.

You can open Package.appxmanifest to further customize properties like the display name, publisher, and capabilities.

To verify the packages were added to your project:

dotnet list package

You should see Microsoft.WindowsAppSDK and Microsoft.Windows.SDK.BuildTools in the output.

Console output (nothing to do)

Because we're building a console app, console output needs to stay in the current terminal. AUMID activation gives a packaged app no console, so a console app would run correctly and print nothing.

winapp handles this for you: an app with OutputType=Exe is launched through an execution alias instead, which inherits your terminal's stdin/stdout/stderr. It adds the required uap5:ExecutionAlias to the manifest it stages, so there is nothing to configure.

UI apps (WPF, WinForms, WinUI) render their own window, so they keep AUMID activation.

To force AUMID for a console app anyway, set the following inside any <PropertyGroup> in dotnet-app.csproj — the app then runs without a console and prints nothing to the terminal:

<WinAppRunUseExecutionAlias>false</WinAppRunUseExecutionAlias>

If you'd rather choose the command name yourself, run winapp manifest add-alias to declare one in Package.appxmanifest; an alias you author is used as-is.

5. Debug with Identity

Since winapp init added the Microsoft.Windows.SDK.BuildTools.WinApp NuGet package to your project, you can simply run:

dotnet run

This automatically invokes winapp run under the hood — creating a loose layout package, registering it with Windows, and launching your app with full package identity.

Arguments you write after dotnet run go to your application, exactly as they would if the project did not reference this package:

dotnet run --devtools          # your app receives --devtools
dotnet run -- --devtools       # identical: the SDK consumes the -- before forwarding

Use -- when your app's flag is also a dotnet run option (--configuration, --framework, --project, -c, -f, -r, ...) — without it the SDK claims the token and your app never receives it:

dotnet run -- --configuration Release   # your app receives --configuration Release

Configure the WinApp launcher itself with the WinAppRun* MSBuild properties. MSBuild consumes these, so they never reach your application:

dotnet run -p:WinAppRunDebugOutput=true --devtools

Here the property configures WinApp while --devtools is passed to your app. See dotnet run support for the full property list, including which properties cannot be combined.

Note

You may see NuGet vulnerability warnings (NU1900) about package sources. These are safe to ignore — they don't affect your build.

You should see output similar to:

Package Family Name: dotnet-app_12345abcde

This confirms your app is running with a valid package identity!

Alternative: Manual `winapp run`

If you didn't use winapp init (or removed the NuGet package), you can build and run manually. winapp run accepts the project directly (project mode) — it builds the .csproj and launches it, so you don't have to point at the build-output folder or build separately:

# Build and run the project in one step (project mode)
winapp run .

# ...or run a specific project / configuration / architecture
winapp run .\dotnet-app.csproj -c Debug --arch x64

To run the project's Native AOT configuration, enable AOT in the project and run:

winapp run . --aot
winapp run . --aot -c Release

Use x64 or ARM64. For a one-time override, append -p PublishAot=true.

You can still point winapp run at a pre-built output folder if you prefer (folder mode):

dotnet build -c Debug
winapp run .\bin\Debug\net10.0-windows10.0.26100.0

Project mode supports both packaged and unpackaged WinUI apps — it detects which from the project's WindowsPackageType and installs the matching-architecture Windows App Runtime automatically. To force an unpackaged run of a packaged project, add -p WindowsPackageType=None.

Multi-project apps (an app referencing class libraries) build correctly: winapp keeps AnyCPU/netstandard2.0 references on their compatible platform instead of forcing the app's architecture across the graph. RID-only remains the default; when the effective configuration requires a self-contained profile (for example, a trimmed Release build), winapp selects the matching profile without changing referenced libraries' platforms.

The dotnet build output streams live, with the exact invocation printed first. Add --verbose for winapp's own build decision traces. Requires .NET SDK 8.0.100 or newer. See winapp run in the usage reference for the full option list.

No Windows SDK installed? C#/WinRT authoring projects normally need a registered Windows SDK to build. When project mode detects none (clean CI, containers, SDK-less dev boxes), it points cswinrt at the winmds from the auto-restored Microsoft.Windows.SDK.NET.Ref package so the build still succeeds — no action needed. It does nothing when an SDK is installed or when you set -p CsWinRTWindowsMetadata=… yourself.

To add the NuGet package back: dotnet add package Microsoft.Windows.SDK.BuildTools.WinApp --prerelease

Tip

To disable the automatic dotnet run integration, add <EnableWinAppRunSupport>false</EnableWinAppRunSupport> to your .csproj. See dotnet run support docs for customization options.

Alternative: Sparse package identity

If you need sparse package behavior specifically (identity without copying files), you can use create-debug-identity instead. This registers a sparse package pointing to your exe rather than creating a loose layout:

winapp create-debug-identity .\bin\Debug\net10.0-windows10.0.26100.0\dotnet-app.exe

Then run the executable directly (do not use dotnet run as it might rebuild/overwrite the file):

.\bin\Debug\net10.0-windows10.0.26100.0\dotnet-app.exe

Alternative: Manual MSBuild target

If you prefer not to use the NuGet package, you can add a custom MSBuild target that runs create-debug-identity after Debug builds. Add this to your .csproj file at the end, just before the closing </Project> tag:

  <!-- Automatically apply debug identity after Debug builds -->
  <Target Name="ApplyDebugIdentity" AfterTargets="Build" Condition="'$(Configuration)' == 'Debug'">
    <Exec Command="winapp create-debug-identity &quot;$(TargetDir)$(TargetName).exe&quot;" 
          WorkingDirectory="$(ProjectDir)" 
          IgnoreExitCode="false" />
  </Target>

With this configuration, dotnet build applies the debug identity and you can run the executable directly. Note that dotnet run may rebuild and overwrite the identity, so run the exe manually after building.

Tip

For advanced debugging workflows (attaching debuggers, IDE setup, startup debugging), see the Debugging Guide.

When to skip this: If you prefer explicit control over when identity is applied, or if you're working on code that doesn't need identity for most of your development cycle, the manual approach above may be simpler.

6. Using Windows App SDK (Optional)

The Windows App SDK gives you access to modern Windows APIs beyond what the base Windows SDK provides — things like the notification system, windowing APIs, app lifecycle management, and on-device AI. If your app needs any of these capabilities, this step is for you. If you just need package identity for distribution, you can skip to step 7.

If you ran winapp init (Step 4), Microsoft.WindowsAppSDK was already added as a NuGet package reference to your .csproj. You can verify with dotnet list package. If you skipped SDK setup during init, or need to add it manually, run:

dotnet add package Microsoft.WindowsAppSDK

Update Program.cs

Replace the entire contents of Program.cs with the following code, which adds a Windows App Runtime version check:

using Windows.ApplicationModel;

class Program
{
    static void Main(string[] args)
    {
        try
        {
            var package = Package.Current;
            var familyName = package.Id.FamilyName;
            Console.WriteLine($"Package Family Name: {familyName}");
            
            // Get Windows App Runtime version using the API
            var runtimeVersion = Microsoft.Windows.ApplicationModel.WindowsAppRuntime.RuntimeInfo.AsString;
            Console.WriteLine($"Windows App Runtime Version: {runtimeVersion}");
        }
        catch (InvalidOperationException)
        {
            // Thrown when app doesn't have package identity
            Console.WriteLine("Not packaged");
        }
    }
}

Build and Run

Rebuild and run the application with Windows App SDK. Since we've added the WinAppSDK, we need to re-register with identity so winapp adds the runtime dependency. If you added the WinApp NuGet package (recommended), simply run dotnet run. Otherwise (replace dotnet-app with your project name):

dotnet build -c Debug
winapp run .\bin\Debug\net10.0-windows10.0.26100.0

You should now see output like:

Package Family Name: dotnet-app.debug_12345abcde
Windows App Runtime Version: 8000.770.947.0

The Windows App SDK NuGet package includes all the necessary assemblies for accessing modern Windows APIs including:

Notifications and live tiles
Windowing and app lifecycle
Push notifications
And many more Windows App SDK components

For more advanced Windows App SDK usage, check out the Windows App SDK documentation.

7. Package with MSIX

Once you're ready to distribute your app, you can package it as an MSIX using the same manifest.

Build for Release

First, build your application in release mode for optimal performance:

dotnet build -c Release

Note

You may see NuGet vulnerability warnings (NU1900). These are safe to ignore and don't affect your build output.

Generate a Development Certificate

Before packaging, you need a development certificate for signing. Generate one if you haven't already:

winapp cert generate --if-exists skip

Sign and Pack

Now you can package and sign. Point the pack command to your build output folder (replace dotnet-app and the TFM path with your project's values):

# package and sign the app with the generated certificate
winapp pack .\bin\Release\net10.0-windows10.0.26100.0 --manifest .\Package.appxmanifest --cert .\devcert.pfx

Note: The pack command automatically uses the Package.appxmanifest from your current directory and copies it to the target folder before packaging. The generated .msix file will be in the current directory.

Tip: You can also skip locating the build-output folder and pack straight from the project — winapp package .\dotnet-app.csproj --cert .\devcert.pfx publishes the project and packages its output in one step (project mode defaults to the Release configuration). Project mode accepts the build options -c, --arch, -f, --no-build, --no-restore, -p; add --no-build to package an existing build without rebuilding.

Install the Certificate

Before you can install the MSIX package, you need to install the development certificate. Run this command as administrator:

winapp cert install .\devcert.pfx

Install and Run

Install the package by double-clicking the generated *.msix file.

Now you can run your app from anywhere in the terminal by typing:

dotnet-app

You should see the "Package Family Name" output, confirming it's installed and running with identity.

Tip

If you need to repackage your app (e.g., after code changes), increment the Version in your Package.appxmanifest before running winapp pack again. Windows requires a higher version number to update an installed package.

Tips

Once you are ready for distribution, you can sign your MSIX with a code signing certificate from a Certificate Authority so your users don't have to install a self-signed certificate.
The Microsoft Store will sign the MSIX for you, no need to sign before submission.
You might need to create multiple MSIX packages, one for each architecture you support (x64, Arm64). Use the -r flag with dotnet build to target specific architectures: dotnet build -c Release -r win-x64 or dotnet build -c Release -r win-arm64.

Automating MSIX Packaging (Optional)

To automate MSIX packaging as part of your Release builds, add this target to your .csproj file (you can add it alongside the debug identity target):

  <!-- Automatically package as MSIX after Release builds -->
  <Target Name="PackageMsix" AfterTargets="Build" Condition="'$(Configuration)' == 'Release'">
    <!-- Package and sign directly from build output -->
    <Exec Command="winapp pack &quot;$(TargetDir.TrimEnd('\'))&quot; --cert &quot;$(ProjectDir)devcert.pfx&quot;" 
          WorkingDirectory="$(ProjectDir)" 
          IgnoreExitCode="false" />
  </Target>

With this configuration:

Building in Release mode (dotnet build -c Release) will automatically create the MSIX package
The MSIX is packaged and signed with your development certificate
The final .msix file will be in the root of the project

You can also create a custom configuration (e.g., PackagedRelease) by modifying the condition to '$(Configuration)' == 'PackagedRelease'.

Next Steps

Distribute via winget: Submit your MSIX to the Windows Package Manager Community Repository
Publish to the Microsoft Store: Use winapp store to submit your package
Set up CI/CD: Use the setup-WinAppCli GitHub Action to automate packaging in your pipeline
Explore Windows APIs: With package identity, you can now use Notifications, on-device AI, and other identity-dependent APIs

Feedback

Was this page helpful?

Last updated on 2026-09-24

Using winapp CLI with .NET

Prerequisites

1. Create a New .NET App

2. Update Code to Check Identity

3. Run Without Identity

4. Initialize Project with winapp CLI

Console output (nothing to do)

5. Debug with Identity

Alternative: Manual winapp run

Alternative: Sparse package identity

Alternative: Manual MSBuild target

6. Using Windows App SDK (Optional)

Update Program.cs

Build and Run

7. Package with MSIX

Build for Release

Generate a Development Certificate

Sign and Pack

Install the Certificate

Install and Run

Tips

Automating MSIX Packaging (Optional)

Next Steps

Feedback

Additional resources

Alternative: Manual `winapp run`