User manual WISE SOLUTIONS WISE FOR WINDOWS INSTALLER 6

[. . . ] Wise for Windows Installer, Version 6. 0 Copyright ©1994-2004 Wise Solutions, Inc. This documentation and the accompanying software are copyrighted materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system or translated into any human or computer language without prior written permission of Wise Solutions, Inc. [. . . ] See Defining and Translating Into Additional Languages on page 260. The default language for all installations is English, unless you change it. For details, see Changing the Default Language on page 271. 276 Language IDs Language IDs Windows Installer uses language IDs to determine whether the destination computer supports the language that is used for the installation dialogs. Example: If you create an installation with the language ID for Greek, that installation only runs on a computer with Greek fonts. Language IDs and Locale Codes for Common Languages For additional language codes, search for "Table of Language Identifiers" and "Language Code and Scripts" in the MSDN Library (msdn. microsoft. com/library). Language Languageneutral Process or User Default Language Czech Danish Dutch Dutch English English English English English English Finnish French French French French German German German Greek Hungarian Icelandic Sublanguage ID (decimal notation) 0 1024 Script Locale Language Code 1029 Danish Belgian (Flemish) Dutch (Standard) American Australian British Canadian Ireland New Zealand Finnish Belgian Canadian French (Standard) Swiss Austrian German (Standard) Swiss 1030 2067 1043 1033 3081 2057 4105 6153 5129 1035 2060 3084 1036 4108 3079 1031 2055 1032 1038 Icelandic 1039 Latin 2 Latin 1 Latin 1 Latin 1 Latin 1 Latin 1 Latin 1 Latin 1 Latin 1 Latin 1 Latin 1 Latin 1 Latin 1 Latin 1 Latin 1 Latin 1 Latin 1 Latin 1 Greek Latin 2 Latin 1 CSY DAN NLB NLD ENU ENA ENG ENC ENI ENZ FIN FRB FRC FRA FRS DEA DEU DES ELL HUN ISL 277 Language IDs Language Italian Italian Norwegian Norwegian Polish Portuguese Portuguese Russian Slovak Spanish Spanish Spanish Swedish Turkish Sublanguage Italian (Standard) Swiss Norwegian (Bokmal) Norwegian (Nynorsk) ID (decimal notation) 1040 2064 1044 2068 1045 Script Latin 1 Latin 1 Latin 1 Latin 1 Latin 2 Latin 1 Latin 1 Cyrillic Latin 2 Latin 1 Latin 1 Latin 1 Latin 1 Ext. Latin (code page 1254) Locale Language Code ITA ITS NOR NON PLK PTB PTG RUS SKY ESM ESN ESP SVE TRK Portuguese (Brazilian) Portuguese (Standard) 1046 2070 1049 1051 Mexican Spain (Modern Sort) Spain (Standard/ Traditional Sort) Swedish 2058 3082 1034 1053 1055 278 Chapter 12 Distributing an Installation When you complete and compile an installation and are ready to deploy it, you can: !! Use Package Distribution to distribute an installation to disk, to the network, or to an FTP server for deployment to end users. Use Package Distribution to perform an administrative installation, which lets end users install from a network. Use WiseUpdate to configure your application for automatic updating. In the Enterprise Edition, you also can use Package Distribution to distribute to the share point directory, so that the installation can be imported into the Software Manager database. 279 Package Distribution Package Distribution Use Package Distribution to deploy or share a package by: !! Copying an Installation to the Share Point Directory. (Enterprise Edition only. ) Copying an Installation to a Network Directory on page 282. Copying an Installation to an FTP Server on page 282. Performing an Administrative Installation on page 283. Copying an Installation to Removable Media on page 284. You can run Package Distribution from Wise for Windows Installer or from Software Manager. Typically, when you run Package Distribution from Wise for Windows Installer, you distribute a project file or the compiled installable file from its source directory. When you distribute from Software Manager, you distribute installable files only (examples: . MSI or . EXE files) from the Software Manager database. Therefore, when you run Package Distribution from Software Manager, the option to distribute to the share point directory is not available. Copying an Installation to the Share Point Directory " Enterprise Edition only. You can use Package Distribution to copy an installation or merge module to the share point directory, for later importing into the Software Manager database. This lets you store all installation information in a centralized location and use Software Manager to manage installation resources. See Sharing Installation Resources on page 34. Distributing to the share point directory does not actually import the package into the Software Manager database, but copies it to a directory in a format that can be imported into the Software Manager database. You use Software Manager to import it from the share point. When you distribute to the share point directory: ! All the installation's source files are copied to the share point directory and the source paths for those files are updated. See Where are Installation Resources Stored? [. . . ] The global version of the assembly can be the version installed with the application or an earlier version. ! ! 542 About Microsoft . NET Technology I thought . NET meant I could use XCOPY to install applications without registration. Why do I need to build a Windows Installer installation? For a . NET application that uses only managed code and private assemblies, the installation process can be as simple as copying files to the destination computer. Most developers, however, still need to create a compressed, single-file installation that is easy to deploy and that provides a friendly interface to the end user. . NET applications that use shared assemblies, or that have a mix of managed and unmanaged code, cannot be installed via XCOPY. [. . . ]