Presentation on theme: "1 Developing multilingual installation programs using InstallShield for Windows Installer David L. Cole IBM Corporation Research Triangle Park, NC"— Presentation transcript:
1 Developing multilingual installation programs using InstallShield for Windows Installer David L. Cole IBM Corporation Research Triangle Park, NC
2 Why were here... Globalized Software Application Globalized Software Application No matter how good your application is, Your customers first experience is... No matter how good your application is, Your customers first experience is... The install program! New technologies exist… - The Windows Installer - Development tools (InstallShield) En De Fr Jp Ko It Which enable sophisticated, multilingual install programs Thats what were here to talk about!
3 Topics ä A background on Microsofts Windows Installer service ä A description of the InstallShield for Windows Installer tool ä Examples of multilingual install programs ä Details on how to design and develop multilingual install programs ä Explanation of how and where Unicode is used in the process ä Hints, tips, and gotchas ä References
4 May have separate languageversions languageversions What is a multilingual installation program? Installation Program Software Application Product to be installed English German... May support multiple languages May support multiplelanguagesconcurrently multiplelanguagesconcurrentlyEnEn DeDe En De Separate Language Versions (CD & App) Separate Language Versions (CD & App) Type I En De... Common CD, separate Application language Versions Common CD, separate Application language Versions Type II EnEn DeDe Common CD & App, multiple language resources Common CD & App, multiple language resources Type III
5 What is the Windows Installer? ä Microsofts Windows Installer is a new installation service that consists of: ä an operating system resident installation service ä a standard format for component management ä a management API for applications and tools. ä Is a key component of Windows 2000, also available for other Windows versions (Windows 95, 98, and NT 4.0) ä Also known as MSI ä Not an authoring environment! ä 3rd party vendors (e.g., InstallShield, Wise) provide development tools
6 Why Windows Installer? ä Better management of shared resources ä Consistent enforcement of installation rules ä Easy customization by administrators ä Facilitated selection of desired application features ä Automatic repair of configuration problems ä In essence: ä reduced support costs for software providers ä a much improved experience for administrators and end-users
7 An operating system resident installation service... ä Part of the operating system! ä Enforces consistent installation rules ä Service is engine for install program data ä Manages shared components on behalf of an application ä Can run at elevated privilege level on Windows NT/2000 ä e.g., non-administrators may install services ä Built-in to Windows 2000, and available on Windows 95, Windows 98, and Windows NT 4.0 ä Use is required for new Certified for Microsoft Windows logo (except for server products, for the time being)
8 A standard format... ä Data for operating system install Engine ä Install program is actually a collection of data tables ä Establishes product / feature / component hierarchy ä Incorporates standard actions such as installing fonts ä Extendable with custom actions ä.msi file extension ä May be opened and extended with development tools such as InstallShield for Windows Installer
9 Components and features ä Atomic unit of installation ä Collection of files, registry keys, etc. that are all installed together ä Uniquely defined and automatically shared by OS ä Not visible to the user ä Typical method of distinguishing OS-specific and language-specific resources ä Groupings of components ä How groups of components are selected to be installed or uninstalled ä Exposed to the user ä Maintains feature state ä Install locally ä Run from source ä Install on demand ä Do not install Components Features
15 A management API for applications and tools... ä Tightly coupled with the Windows Shell ä Manages file paths on behalf of an application ä enables roaming user support ä Ensures that requested applications/features are both installed and complete ä enables install-on-demand (Advertising) ä enables self-repair ä Maintains an inventory of installed applications/features ä Plays role in enforcing system policies
16 InstallShield for Windows Installer (ISWI) ä A development tool for authoring Windows Installer-based install programs ä Creates data tables which compose the.msi file ä Includes wizards for stepping you through ä creating a standard project ä compiling the.msi file and building the output media ä creating custom action controls ä creating components ä adhering to best practices ä Also includes support for creating multilingual installs!
17 ISWI input and output Installation logic and user interface design Application files, registry settings, shortcuts, etc. Feature and component design ISWIISWI ISWIISWI Setup.exe Windows Installer service.msi file Language transforms Application files Note: numerous different build options exist
18 Setup.exe function flow ä Determine default language (via user locale) ä Display language selection panel ä Query Windows Installer version ä Install Windows Installer service, if needed ä Launch Windows Installer service (msiexec.exe) ä Apply selected language transform ä Install product ä Pass command line parameters
19 Component 1 (Global_Default_Executables) Component 3 (Global_Default_Help) Component 2 (Global_Default_DLLs) Product(Demo) Feature 2 (DefaultHelpFiles) Feature 1 (DefaultProgram) Entry Point (Shortcut) Resource(sol.exe) Resource(sol.chp) Resource(sol.hlp) Resource(cards.dll) A demo of ISWI
20 Localizing an install program ä Add entries to English (or default) string table for any translatable text used in messages or added to dialogs ä Ensure that custom messages and dialogs reference string table entries ä Export string table of default language and translate into supported languages ä Import translated string table for each language ä InstallShield-provided strings are already translated but may be edited ä Verify controls on custom dialogs are properly sized ä Thats it!!
21 Designing a multilingual install program - Type I ä Language chosen at product build time ä Set of supported languages selected via Project Wizard or Project Properties ä Language-dependent components identified via Languages field of each component (Setup Design view) ä At build time (using the Release Wizard), ä filter application by selected language (Filtering Settings dialog) ä Include only the selected language and make default (Setup Languages dialog) ä Result: single language version of application, with matching language of install program En De Separate Language Versions (CD & App) Separate Language Versions (CD & App) Type I
22 Designing a multilingual install program - Type II ä Language chosen at product install time ä Set of supported languages selected via Project Wizard or Project Properties ä Language-dependent components identified via Conditions field (ProductLanguage property) of each component (Setup Design view) ä At build time (using the Release Wizard), ä do not filter application by language ä Include all languages, and check Display the Setup Languages dialog (Setup Languages dialog) ä Result: setup.exes language selection panel chooses language version of application and language of install program En De... Common CD, separate Application language Versions Common CD, separate Application language Versions Type II
23 Designing a multilingual install program - Type III ä Language chosen at product run time ä Applications user interface should include controls to choose language (good to couple with install on demand) ä Set of supported languages (for install program) selected via Project Wizard or Project Properties ä Design feature/subfeature tree to list supported languages (allows user to easily add or remove languages) ä At build time (using the Release Wizard), ä do not filter application by language ä Include all languages, and check Display the Setup Languages dialog (Setup Languages dialog) ä Result: setup.exes language selection panel chooses language of install program; user selects language version(s) of application to be installed. EnEn DeDe Common CD & App, multiple language resources Common CD & App, multiple language resources Type III
24 Use of Unicode ä Character strings within the.msi file ä Exported string files (both Unicode and ASCII text) ä License Agreement text (.rtf file) ä MSI program interfaces
25 Hints, tips, and gotchas ä Must install Windows language resources ä New Language Wizard ä command syntax for logging ä MsiZap ä Additional tets scenarios ä Multiple files of same name to same target directory ä Filtering components with a property set in the UI sequence ä Windows 95 bug re: dropdown list on language selection panel ä Adding language packs to an existing project
26 Resources ä The Windows Installer Service, a white paper from Microsoft, available at ä "Roadmap to Windows Installer Documentation" in the Microsoft Platform SDK, and online at ä Application Specification for Microsoft Windows 2000 for distributed applications Version 1.0, available at ä InstallShield for Windows installer web page at ä InstallShield Knowledge Base at ä InstallShield for Windows Installer news groups at news server news.installshield.com ä installshield.iswi.general ä installshield.iswi.customaction ä installshield.iswi.international ä InstallSite web site at
27 Supplemental Slides The following slides show the language features of InstallShield for Windows Installer, and the accompanying text explains how these features are used to create the different types of multilingual installation programs.