Skip to content

rust.md

Latest commit

 

History

History
217 lines (155 loc) · 6.85 KB

rust.md

File metadata and controls

217 lines (155 loc) · 6.85 KB

Using winapp CLI with Rust

This guide demonstrates how to use winappcli with a Rust application to debug with package identity and package your application as an MSIX.

For a complete working example, check out the Rust sample in this repository.

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 cargo build) does not have package identity. This guide shows how to add it for debugging and then package it for distribution.

Prerequisites

  1. Rust Toolchain: Install Rust using rustup or winget:

    winget install Rustlang.Rustup --source winget

  2. winapp CLI: Install the winapp tool via winget:

    winget install microsoft.winappcli --source winget

1. Create a New Rust App

Start by creating a simple Rust application:

cargo new rust-app
cd rust-app

Run it to make sure everything is working:

cargo 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 crate to access Windows APIs.

First, add the windows dependency to your Cargo.toml by running:

cargo add windows --features ApplicationModel

Next, replace the contents of src/main.rs with the following code. This code attempts to retrieve the current package identity. If it succeeds, it prints the Package Family Name; otherwise, it prints "Not packaged".

Note: The full sample also includes code to show a Windows Notification if identity is present, but for this guide, we'll focus on the identity check.

use windows::ApplicationModel::Package;

fn main() {
    match Package::Current() {
        Ok(package) => {
            match package.Id() {
                Ok(id) => match id.FamilyName() {
                    Ok(name) => println!("Package Family Name: {}", name),
                    Err(e) => println!("Error getting family name: {}", e),
                },
                Err(e) => println!("Error getting package ID: {}", e),
            }
        }
        Err(_) => println!("Not packaged"),
    }
}

3. Run Without Identity

Now, build and run the app as usual:

cargo 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 sets up everything you need in one go: app manifest and assets.

Run the following command and follow the prompts:

winapp init

When prompted:

  • Package name: Press Enter to accept the default (rust-app)
  • Publisher name: Press Enter to accept the default or enter your name
  • Version: Press Enter to accept 1.0.0.0
  • Entry point: Press Enter to accept the default (rust-app.exe)
  • Setup SDKs: Select "Do not setup SDKs"

This command will:

  • Create appxmanifest.xml and Assets folder for your app identity

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

5. Debug with Identity

To test features that require identity (like Notifications) without fully packaging the app, you can use winapp create-debug-identity. This applies a temporary identity to your executable using the manifest we just generated.

  1. Build the executable:

    cargo build

  2. Apply Debug Identity: Run the following command on your built executable:

    winapp create-debug-identity .\target\debug\rust-app.exe

  3. Run the Executable: Run the executable directly (do not use cargo run as it might rebuild/overwrite the file):

    .\target\debug\rust-app.exe

You should now see output similar to:

Package Family Name: rust-app_12345abcde

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

6. Package with MSIX

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

Prepare the Package Directory

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

cargo build --release

Then, create a directory to hold your package files and copy your release executable.

mkdir dist
copy .\target\release\rust-app.exe .\dist\

Add Execution Alias

To allow users to run your app from the command line after installation (like rust-app), add an execution alias to the appxmanifest.xml.

Open appxmanifest.xml and add the uap5 namespace to the <Package> tag if it's missing, and then add the extension inside <Applications><Application><Extensions>...:

<Package
  ...
  xmlns:uap10="http://schemas.microsoft.com/appx/manifest/uap/windows10/10"
+ xmlns:uap5="http://schemas.microsoft.com/appx/manifest/uap/windows10/5"
  IgnorableNamespaces="uap uap2 uap3 rescap desktop desktop6 uap10">

  ...
  <Applications>
    <Application ...>
      ...
+     <Extensions>
+       <uap5:Extension Category="windows.appExecutionAlias">
+         <uap5:AppExecutionAlias>
+           <uap5:ExecutionAlias Alias="rust-app.exe" />
+         </uap5:AppExecutionAlias>
+       </uap5:Extension>
+     </Extensions>
    </Application>
  </Applications>
</Package>

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:

winapp pack .\dist --cert .\devcert.pfx

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

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:

rust-app

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

Tips:

  1. 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
  2. The Microsoft Store will sign the MSIX for you, no need to sign before submission.
  3. You might need to create multiple MSIX packages, one for each architecture you support (x64, Arm64)