Why convert WAPPROJ to APPX?
A .wapproj is an MSBuild project file, not a distributable - developers compile it to an .appx (or the newer .msix) so the app can be sideloaded or submitted to the Store.
How to convert WAPPROJ to APPX
Visual Studio Create App Packages EASIEST
Right-click the packaging project, choose Package and Publish | Create App Packages, pick Sideloading, and Visual Studio writes the .appx/.msix to the AppPackages folder.
MSBuild command line FREE
Run msbuild MyApp.wapproj -p:Configuration=Release -p:Platform=x64 -p:UapAppxPackageBuildMode=SideloadOnly to produce the .appx/.msix without opening the IDE.
MakeAppx.exe FREE
For a hand-built layout, run the Windows SDK's makeappx pack /d <layout> /p output.appx to package files into an .appx directly.
About these formats
A .wapproj file is a Windows Application Packaging Project used in Visual Studio to package a desktop app (Windows Forms, WPF, or Win32) as an MSIX or APPX package for the Microsoft Store…
Open .WAPPROJ details →An APPX file is a Windows app installation package introduced with Windows 8. On Windows 10/11, double-click it and the built-in App Installer handles it, or run Add-AppxPackage -Path…
Open .APPX details →Quality & what to watch
- New projects default to the
.msixformat; choose.appxexplicitly if you specifically need the older extension. - The output must be code-signed to install; an unsigned
.appxwon't sideload without a trusted certificate. - Stale
obj,bin,AppPackagesandBundleArtifactsfolders often break the build - delete them if packaging fails.
Frequently asked questions
Is .wapproj the same as .appx?
.wapproj is the project you build; the .appx/.msix is its packaged output.Can I build without Visual Studio?
msbuild on the .wapproj produces the package from the command line.Why won't my .appx install?
Should I use .appx or .msix?
.appx only if a target requires it.