Making a CAB file in accordance with Microsoft standards

For the program on the WindowMobile, Microsoft has a very detailed request file "Designed for WindowsMobileTM Software Application Handbook for Smartphone".

This document is generally very clear, which is very clear inside, but it is very puzzled about the parameters NounInstall.

First according to:

Required: Packages Must Have Setup XML (Smartphone WAP Provisioning)

The setup xml is generated automatically by bagwizsp. If you wish to create your cap

Manually, You will Also Have to create this setup XML manload.

We can generate a CAB file with an INF file written by CabwizSP.

Commands such as CabwizSp d: /gbcab/fordopod.inf / dest d: / GBCAB / CPU ARM4

The format of the INF file can be referred to:

Http://msdn.microsoft.com/library/en-us/wcesetup/html/_wcesdk_creating_an_inf_file_for_the_cab_wizard.asp?frame=true

But look at the second request:

Required: Provisioning XML File Must Include Install CSP XML with NounInstall

THE Provisioning XML File SHOULD INCLUDE An Install CSP Section At The Start of The

Document, Just Below The Element. This Install CSP XML Should

Also include The NounInstall Parm.

Trouble!

There is no NOUNISTALL parameter in the CAB file generated by the CabwizSP!

From Microsoft's information, the nouninstall parameter is set to make the application do not generate any uninstall related information when installing, if there is no such parameter in _Setup.xml, the default is to generate uninstall information. If there is one parameter in _Setup.xml, and the value is 1, then after the installation package is installed, it will not return to generate any uninstall information, then the "delete program" is not found in the "Remove Programs" CAB. .

After checking the information, you will find that the CabwizSP can bring a parameter / nouninstall, but you will find this parameter, add this parameter, the bagwizsp can generate a _Setup.xml with a NounInstall parameter, but in fact, this parameter The value is 1, causing your application to uninstall!

Can't uninstall, obviously can't pass test!

Because Microsoft has such requirements:

Required: Application Must Install / UnInstall Correctly

Finally, I have to solve the contents of the CabwizSP's CAB file (Windows you can decompressed, of course you can also use WinRAR). Modify the _Setup.xml file (in ), then use Makecab to re-package file, of course possible You also need Cabsigner to sign your CAB file. Before using Makecab, you need to generate a DDF file with the following:

.SET CABINET = ON

.Set compress = OFF

.SET CABINETFILECUNTTHRESHOLD = 0; No Files Per Cabinet Threshold

.Set folderfilecountthreshold = 0; No Files Per folder threshold

.Set foldersizetHold = 0; No Folder Size Threshold

.Set Maxcabinetsize = 0; no max size for the capacity

.Set MaxDiskFileCount = 0

.Set maxdisksize = 0

.Set reservepercabinetsize = 6144; for web signing

.Set reserveperdatablocksize = 0

.Set reserveperfoldersize = 0

.Set uniquefiles = off

.SET DiskDirectory1 = D: / GBCAB

.Set Disklabel1 = setup

;

To be filled out by the bagwiz.exe program

; .Set inffilename =

;.SET RPTFileName =

;.SET CABINETNAME1 =

;

Followed by the list of files

.Set InffileName = C: /Docume ~ 1/admini ~ 1/locals ~ 1/temp/wiz4ec.tmp

.Set rptfilename = c: /docume ~ 1/admini ~ 1/locals ~ 1/temp/wiz4ed.tmp

.SET CABINETNAME1 = YOURTARGET.CAB

.Set reserveperfoldersize = 32

.Set compress = on

This is the path of the _Setup.xml file and the path to the setup file

The format is: the source file full path _Setup.xml corresponds to the file name

D: /Gbcab/_setup.xml _Setup.xml

D: /Gbcab/setup.dll 000setup.999

.New folder

Here is the list of your files.

The format is: the source file full path _Setup.xml corresponds to the file name

D: /GBCAB /EB_EN.EBD 000EB_EN.004

D: /Gbcab/eb_sc.ebd 000EB_SC.003

Then use the command:

Makecab / f d: /gbcab/your.ddf

You can generate yourtarget.cab; then you can sign your own CAB using Cabsigner.

Designed for WindowsMobileTM Software Application Handbook for SmartPhone also made a request for other aspects. I feel that we need to pay attention to: 1. The DLL file can only be placed in the / storage / windows directory or the program itself (of course I just target non-ROM programs).

2. The / storage / windows and / windows directory can only place a DLL.

3. The program's directory must be under the / storage / program file below.

4. The program must be able to uninstall normally, please note: If your program always keeps one or more files that you installed by the file, your program is not able to uninstall, but read only There is no problem.

5. After the program is uninstalled, it should be able to automatically clear all files (including files generated after the program installation) and the registry key.

6. The SMARTPHONE style must be followed on the interface, such as right-click menu, Spinner control, etc.

7. No program does not prevent the user from answering the phone.

There are not many other parts, and everyone carefully controls the Designed for WindowsMobileTM Software Application Handbook for Smartphone.