WAPPROJ MSIX
File conversion

Convert WAPPROJ to MSIX

QUICK ANSWER
Is it possible to convert WAPPROJ to MSIX?
Yes - WAPPROJ converts to MSIX.

The .wapproj is the recipe; the .msix is the baked result. In Visual Studio use Project > Publish > Create App Packages, or on the command line run MSBuild against the .wapproj with the packaging properties set. Either way you get a signed .msix ready to sideload or submit to the Store.

Also to MSIX: OSD · APPX · EMSIXBUNDLE

On this page

Tested on macOS, Windows & Linux
Last verified Sep 2026

More free converters

HEIC, PNG, WEBP, MP3 and more - every tool here is free.

Open the toolbox

Why convert WAPPROJ to MSIX?

A Windows Application Packaging Project exists precisely to output an .msix package for a desktop or UWP app. Developers reach for this when they want to distribute a Win32/WPF/WinUI app through modern MSIX installers or the Microsoft Store, and the .wapproj bundles the manifest, assets and dependencies into that package.

How to convert WAPPROJ to MSIX

MSBuild command line FREE

Run msbuild MyApp.wapproj /p:UapAppxPackageBuildMode=SideloadOnly /p:AppxBundle=Never /p:AppxPackageDir=out\ to build the .msix without the IDE. Add /p:AppxPackageSigningEnabled=true with a certificate to sign it.

MSIX Packaging Tool (installer capture) FREE

If you have no source project, Microsoft's MSIX Packaging Tool can convert an existing .exe/.msi installer into an .msix by capturing its install. This bypasses the .wapproj entirely.

About these formats

Quality & what to watch

  • The output must be code-signed with a trusted certificate before Windows will install it outside the Store.
  • MSIX runs the app in a lightweight container, so features like drivers, kernel services or arbitrary registry writes may be blocked or virtualized.
  • Store submission bundles are built with AppxBundle=Always; sideload builds usually use Never - pick the mode that matches your distribution.

Frequently asked questions

What is the difference between .msix and .msixbundle?
An .msix targets one architecture; an .msixbundle packs several architecture packages together for the Store.
Do I need Visual Studio to build it?
No. MSBuild from the Visual Studio Build Tools can build the .wapproj headlessly in CI.
Why won't my .msix install?
It is almost always signing: the package must be signed with a certificate the machine trusts.
Can I make an MSIX without any source project?
Yes, use the MSIX Packaging Tool to capture and convert an existing installer.