ElCondor · Apr 25, 2010 at 03:22 pm

Windows Phone 7 Facts: .xap to Replace .cab

XDA member and moderator Da_G has showed us some interesting facts about Windows Phone 7 in the WP7 Development and Hacking section. In the following weeks, we will be covering the more technical side of the currently unreleased OS by Microsoft. We’ll try to make it as easy to read as possible, so get yourself a cup of coffee, sit back, and read!

Most of you probably know about the .cab files. We’ll be talking about the Cab file used for Windows Mobile. Cab files are nothing more than installation packages that copy the files and registry edits from the package to the desired folder on your device. These ‘cabinet’ files, which originally were called ‘Diamonds’,  were used since the very first Windows Mobile devices.

Well these files seem to get banished from the coming Windows Phone 7, internally still called Windows Mobile 7. The new files to replace the cabinets are called ‘.xap’ files. So what are the exact changes between the two files?

First of all, .xap files are nothing more than renamed .zip files. There are a number of possible .xml files that could be included inside the .xap. These determine things like required security access level, to tell the system which .dll contains the main() for the application, and more setup options. Initially, xap files will only be available for deployment through the Marketplace.

Because of the sometimes bad experiences from users about laggy and slow Stock ROMs, Microsoft added some very strict requirements for preloaded apps:

Originally posted by Da_G

Preloaded App Requirements (which will be distributed as .xap) as follows:

  • Maximum of 6 preloaded applications on the device, not to exceed 60MB
  • All preloaded apps must pass Marketplace submission process (some extended APIs are available to OEM/MO so the process is slightly relaxed in that regard)
  • The application(s) and all future updates must be free of charge.
  • The apps must launch without dependency on network availability.
  • The apps must persist through a “hard reset”.
  • The apps must be updatable and revocable (!!!!) through the Marketplace.
  • The apps must notify the user at first launch of any capabilities to be utilized and get user consent (to access compass, accelerometer, network, etc.)

Most of the requirements aren’t bad at all for the end-user, though I think the OEMs are probably not very happy with these requirements.

You can download an .xap file from the thread to examine it.


_________
Want something on the XDA Portal? Send us a tip!

ElCondor

ElCondor is an editor on XDA-Developers, the largest community for Android users. View ElCondor's posts and articles here.
Mathew Brack · May 28, 2015 at 09:59 pm · 4 comments

I/O Summary: How Android M Handles Power And Charging

In the spirit of improving the core Android experience, Google is changing Android M to be smarter about managing power. Their new Doze feature comprises of two primary roles which allow Android to use motion detection in order to predict activity, and go into deep sleep at the right time based on accelerometer readings.   In order to extend your screen off battery life, Android M will now monitor your activity levels and if it detects that your device has...

XDA NEWS
Mario Tomás Serrafero · May 28, 2015 at 09:51 pm · 3 comments

I/O Summary: Google Photos App

At I/O 2015, Google tackled the information problem in mobile once more, this time through pictures: “how incredible is it that we all have a camera in our pockets at any moment? (...) These moments tell your story (...)[but] taking more pictures and videos makes it harder to relieve memories due to the sheer volume”. This is why they are revamping Google Photos and centering it around 3 big ideas:   Creating a home for all photos and videos that is...

XDA NEWS
Mario Tomás Serrafero · May 28, 2015 at 09:26 pm · 4 comments

I/O Summary: Development, Play Store, The Next Billion

VP of Engineering Jen Fitzpatrick began talking about what Google is doing to help “the next billion” come online. More and more people are getting their first smartphone, and for many people this first phone will be their first computer.   The majority of the next billion will be Android users and they “want to remove the barriers of smartphone adoption”. While there are huge displays of phones on sale, not all are able to run the latest and greatest...

XDA NEWS
Share This