| File / Directory | Purpose |
|----------------|---------|
| AppManifest.xaml | Declares the application identity, version, entry point assembly, and capabilities (e.g., ID_CAP_NETWORKING). |
| WMAppManifest.xml | Windows Phone-specific manifest. Defines title, publisher, supported resolutions, splash screen, and tile templates. |
| [AppName].dll | Compiled C#/VB.NET assembly (for Silverlight apps) or Windows Runtime component (for 8.x+). |
| [AppName].exe (rare) | Present only for native C++ Direct3D apps (Windows Phone 8+). |
| Assets/ | Icons, background images, and splash screens for multiple resolutions (e.g., ApplicationIcon.png, Background.png). |
| Microsoft.Phone.dll (reference) | Not embedded; referenced by the app during runtime. Not part of the XAP. |
Focus: Hacked, developer-unlocked, and homebrew
XDA is where the magic happens. Search for threads titled "[REQ] Working XAP Archive for Lumia 520" or "Collection of Offline XAPs." This is the most reliable source for interop-unlocked XAPs—files that bypass the signature check entirely. windows phone xap archive
With no official method to download apps, the "Windows Phone XAP Archive" emerged as a grassroots preservation movement.
You can’t just download and double-click. You need a time machine (or a PC with Windows 10). Here is the 2026 workflow: | File / Directory | Purpose | |----------------|---------|
Heads up: Many XAPs require a live server to function. If the app was a cloud-based to-do list or a weather widget, it’s likely a brick. Focus on offline games and tools.
XAPs for Windows Phone 7.x contained CIL (Common Intermediate Language) assemblies, which were JIT-compiled on the device. Starting with Windows Phone 8, Microsoft introduced MDIL (Machine-Dependent Intermediate Language) for better performance and security. In MDIL: You can’t just download and double-click
This means that a XAP generated for Windows Phone 7 cannot run on Windows Phone 8 without recompilation, and vice versa (though 8 devices could run 7.x XAPs via a bundled “7.x compatibility layer”).