|
Navigation: »No topics above this level« Windows Mobile Components |
|
Windows Mobile components work analogously the Components. It is a way to group the Windows Mobile files, and allow the end-user choose which files to be installed.
Each Windows Mobile component correspond to a set of Windows Mobile packages. The Default Windows Mobile component, defined in all VisualSetup projects, corresponds to the Windows Mobile packages generated by the device files, device shortcuts and device registry's entries that have the Component property empty. The Component property of device files, device shortcuts and device registry's entries refers to a Windows Mobile component. The Component property of all other project items, like desktop files, Palm files, desktop shortcuts, etc, refers to a Component.
Actually, the end-user cannot choose directly the Windows Mobile components that will be installed. Each Windows Mobile component has the Component property that refers to a Component. The end-user can choose the components that will be installed, not the Windows Mobile components. If you create a component for each Windows Mobile component, and associate each Windows Mobile component with the component correspondent, you will allow the end-user choose which Windows Mobile components that will be installed.
Another utility of Windows Mobile components is to workaround the Windows Mobile limitation of 998 files for each CAB file.Creating Windows mobile components, you can divide the files into different CAB files, and install all the files in the same installation. This will be a friendly solution for this limitation.
To define a Windows Mobile component, open the Windows Mobile Components' editor (Windows Mobile > Windows Mobile Components menu command), and then select Editor > Add Windows Mobile Component menu command.
The available properties are:
Conditional Information
Component |
The component related to the Windows Mobile component. |
Conditions |
The conditions used to either install or not install the Windows Mobile component. For more information about writing condition, read the Logical Expressions topic. |
Language |
The language of the Windows Mobile component. Before selecting the language you want, you must to define it in the Setup Languages editor. |
Events Information
ARM Setup DLL |
The ARM processors' family external setup DLL that will be included in the Windows Mobile component. |
CEF Setup DLL |
The CEF processors' family external setup DLL that will be included in the Windows Mobile component. |
MIPS Setup DLL |
The MIPS processors' family external setup DLL that will be included in the Windows Mobile component. |
SH3 Setup DLL |
The SH3 processors' family external setup DLL that will be included in the Windows Mobile component. |
SH4 Setup DLL |
The SH4 processors' family external setup DLL that will be included in the Windows Mobile component. |
Use Click-Script Events |
Define if the Windows Mobile component will either use the click-script events you have coded or use the external setup DLL. |
Windows Mobile Component
Attributes |
The attributes of the Windows Mobile files in the output directory. |
Company |
The company's name of the Windows Mobile component. |
Description |
The description of the Windows Mobile component. |
Desktop Dir |
The desktop destination directory of this Windows Mobile component. |
Is Project Sub-Component |
Defines if the Windows Mobile component is a sub-component of current project or an external component. |
Name |
The name that identifies the Windows Mobile component. |