tauri-windows-distribution_skill

Overview

This skill guides developers through distributing Tauri v2 applications on Windows. It explains how to produce MSI and NSIS installers, customize installer behavior, manage WebView2 installation modes, and prepare packages for Microsoft Store submission. Practical examples cover cross-platform NSIS builds, WiX customization, signing, and troubleshooting.

How this skill works

The skill walks through configuration options in the Tauri bundle settings and shows how to swap WiX templates, add WiX fragments, and inject NSIS hooks. It explains WebView2 modes (bootstrapper, embedded, offline, fixed) and how each affects installer size and network requirements. It also details store-specific build settings, code signing, and build commands for local and cross-platform builds.

When to use it

• Shipping a desktop Windows app with a traditional MSI installer for enterprise customers.
• Creating a single EXE installer via NSIS that can be built on Linux or macOS.
• Distributing apps through the Microsoft Store with offline WebView2 support and required metadata.
• Needing custom registry entries, install hooks, or localized installers.
• Building for multiple CPU targets (x86_64, i686, aarch64) and handling cross-compilation.

Best practices

• Choose NSIS for cross-platform developer builds and WiX/MSI for Windows-native enterprise installers.
• Select a WebView2 install mode based on connectivity: downloadBootstrapper for smallest installers, offlineInstaller for air-gapped deployments.
• Sign installers with a valid code-signing certificate and include a timestamp URL to prevent signature expiration issues.
• Use WiX fragments and NSIS hooks for custom registry entries, VC++ runtime installation, and pre/post install tasks.
• Test both perUser and perMachine modes and provide clear language selection for international users.

Example use cases

• Build an NSIS installer on macOS using cargo-xwin and include an installer hook to install prerequisites.
• Create an MSI for enterprise deployment with custom WiX fragments that write registry keys and set install directories.
• Prepare a Microsoft Store package using an offline WebView2 installer, custom publisher name, and generated store icons.
• Require a minimum WebView2 version in the NSIS config to ensure runtime compatibility.
• Enable Windows 7 support by embedding the WebView2 bootstrapper and enabling windows7-compat in Cargo.toml.