archive-com.com » COM » E » EMCOSOFTWARE.COM

Total: 393

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Low-Level Repackaging - MSI Package Builder
    successful repackaging so it is required that you fully understand those steps The advantage of the low level repackaging is the fact that you are not limited by any single repackaging technique and can combine those techniques to reach the desired goal For example you can monitor the installations that do not support silent deployment and wrap the installations that do support it creating a single MSI package for deploying all these installations simultaneously You can also make some corrections to the monitoring results if it is required When you are using the feature of capturing changes to the underlying operating system in a scope of advanced monitoring you must prepare the created project before creating an MSI package Preparation consists of several important steps Firstly MSI Package Builder should copy all file system resources to a project storage If there are any problems during the copying process the problematic files and folders are marked as missing links The problems with missing links must be resolved before proceeding with the MSI generation For an MSI package to be correctly installed on different operating systems with different environment configurations it is required to replace all paths that represent the system folders with a special system folder object All those steps are described in detail within the Projects Preparation section of this document When providing the required changes manually you just create a project to contain those changes and then provide the changes to the project The detailed information about providing and modifying the changes is available in the MSI Projects section of this document The packages to be deployed together with an MSI package those are wrapped packages are provided in the Wrapped Packages view in the same manner as when performing repackaging via wrapping For the detailed information about wrapping

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/low-level-repackaging (2016-05-01)
    Open archived version from archive


  • How should I configure the repackaged installations to support an upgrade? - MSI Package Builder
    packages to be deployed and upgraded correctly they should be properly identified For each MSI package there is a Product GUID that uniquely identifies the product and an Upgrade GUID that is used for matching upgrades Windows Installer maintains its database and handles its consistency depending on these identifiers These identifiers are defined on a project scope while creating and an MSI package or in the Project Details view Pic 1 Identifying the generated MSI package The Product GUID value for the different versions of the installations being repackaged should differ and the Upgrade GUID value should match So for example if we are using the GUIDs displayed on while repackaging the Abode Reader 10 1 0 installation the same Upgrade GUID in combination with another Product GUID must be used for the Abode Reader 10 3 1 installation If you have lost the project used to create a previous version of the MSI package thus cannot find GUIDs used to identify that project you can import that package You ll find the required GUIDs in the Project Details view when the package created on a basis of the import result is selected It is also required that at least one of the first three version figures of the MSI package used for upgrade differs from the version of the previously generated package For example if we have used the 1 0 0 version of the MSI package while repackaging the Abode Reader 10 1 0 installation then we can use 1 1 0 version for the Abode Reader 10 3 1 but we cannot use 1 0 0 3 If you are going to repackage only a single installation into an MSI package but not a suit of applications it is recommended to use the application version as the

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/how-should-i-configure-the-repackaged-installations-to-support-an-upgrade (2016-05-01)
    Open archived version from archive

  • User Interface Page - MSI Package Builder
    installations repackager and as an advanced packages editor That is why different user interface configuration may be required for different persons The configuration is performed on the User Interface preference page To access this page click the Preferences button from the Application Menu and select the appropriate link in the navigation bar on the left in the Preferences dialog within the MSI Package Builder group Pic 1 Configuring user interface For those who use it as a simple repackager it might be enough to walk through the repackaging wizard and build a resulting MSI package so it would be convenient for them to display the Repackage Installation wizard on start up But it is not convenient for those who are using the program also for managing the software packages or creating their own packages Also it is possible to define if the MSI package creation is always run in background The other aspect is a decision making By default after each MSI package creation the program asks if the folder containing the newly created package should be opened in Windows Explorer If your answer is always the same you can answer this question only once on the User Interface page

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/user-interface-page (2016-05-01)
    Open archived version from archive

  • Projects Management - MSI Package Builder
    available The detailed information on the package import is available in the Importing MSI Package section of this document New The New button from the Project Management group on the Home Ribbon page should be used to create a new project To create a new project in MSI Package Builder you can choose the New Project item from the Projects view pop up menu or press the New button from the Project Management group on the Home Ribbon page Alternatively you can click the New Project link in the Recent Projects group on the Welcome Screen The New Project dialog will appear on the screen The same pane is also displayed if you choose the Create New Project option in the Project Setup Wizard Pic 2 Creating a new project You are proposed to specify a name for the project to be created You should pay enough attention to a project name it will help you to identify the project in future Open The Open button from the Project Management group on the Home Ribbon page allows you to open projects available in the projects storage When you close MSI Package Builder all the projects you were working with are automatically closed too It is also possible to close projects manually this will be described further If you want to continue working with those projects that were closed you should open them again The links to the projects you have used recently are available in the Application Menu and in the Recent Projects group of the Welcome Screen To open any of those projects simply click on a link To open projects choose the Open Project item from the Projects view pop up menu or press the Open button from the Project Management group on the Home Ribbon page Alternatively you can click the Open Project link in the Recent Projects group on the Welcome Screen The Open Project dialog will appear on the screen The same pane is also displayed if you choose the Open Existing Projects option in the Project Setup wizard Pic 3 Opening existing projects You can select both single and multiple projects in the Available Projects table to be opened at the same time It is also possible to delete a project from the projects storage if you have noticed that it is no longer needed using the Delete Projects button from the toolbar Close The Close button from the Project Management group on the Home Ribbon page should be used to close the selected projects thus remove them from the Projects view Close All The Close All button from the Project Management group on the Home ribbon page allows you to close all currently opened projects thus remove them from the Projects view MSI Package Builder provides you with an ability of always keeping the Projects view in an actual state You can always close the projects you are not going to work with right now and they will be removed from the view

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/projects-management (2016-05-01)
    Open archived version from archive

  • Projects Preparation - MSI Package Builder
    button from the Links group on the Project Ribbon page when the project is selected As soon as the preparing operation is completed you can see if it has actually succeeded by taking a look at the overlay arrow icon If the arrow is green than the whole projects is prepared successfully and if it is yellow than there were problems during the preparation process In most cases this means that some files were missing when the preparation was executed The detailed information about errors is available in the application log Missing Links The Missing Links drop down button from the Links group on the Project Ribbon page allows you to choose the method for resolving the problems with missing files in the selected projects You can either remove those files or try to check if they became available If the file was not accessible during the preparation process thus not copied to the project storage it is marked as missing For the easier identification of the missing links a broken chain overlay icon is displayed in the left top corner of the items in the File System view The problems with missing links should be resolved before creating an MSI package There are two possible scenarios of solving the missing links problem repair and remove Before choosing a resolution mode you should analyze the problems If the missing files are temporary or not required to be created by the installer during a deployment of a generated MSI package they can be painlessly removed Otherwise you should provide access to those files and repair the missing links You should use the Missing Links drop down button from the Links group on the Project Ribbon page to resolve problems with missing links Roll All The Roll All button from the System

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/projects-preparation (2016-05-01)
    Open archived version from archive

  • File System Modifications - MSI Package Builder
    To add a new file modification select the drive folder or system folder to add modification to and either choose the New File item from the pop up menu or press the File button from the New group on the File System contextual Ribbon page The New File dialog will appear on the screen to configure the file modification Pic 4 Adding a file modification to a project While configuring a file modification you should specify a file name and an operation to be performed over this file during an MSI package installation You can choose between Create Modify and Delete operations For the file creation and modification you should define file content in the Content field providing a path to an existing file to get content from While specifying files and folders modifications you can provide a relative path to the Name field the missing path elements will be automatically created in the file system modifications It is also possible to override file system attributes to be used for the file and specify if this file should be treated as persistent thus not removed during an MSI package uninstall process These options are available in the Advanced Options group The advanced options are provided for the experienced users Please do not modify these options until you are absolutely sure that this modification is required for the correct package deployment MSI Package Builder allows you to create shortcuts to any item defined in the file system modifications during an MSI package installation To add a shortcut definition select the path you would like to create shortcut in and choose the New Shortcut item from the pop up menu Alternatively you can use the Shortcut button from the New group on the File System contextual ribbon page The New Shortcut dialog will appear on the screen to let you configure the shortcut Pic 5 Adding a shortcut to a project While adding a shortcut you should provide a name for the shortcut to be created to the Name field and choose the shortcut target in the Target field Optionally you can configure a set of additional shortcut settings You can choose a working directory for a shortcut choose a required window state provide command line arguments to be passed to the shortcut target and define a comment for the shortcut The Arguments field supports the property definition placeholders so you can use the standard MSI properties while specifying the arguments See the Property Definition Placeholders section of this document for the list of available placeholders Edit The Edit button from the Management group on the File System contextual Ribbon page should be used to change the selected file system modification Delete The Delete button from the Management group on the File System contextual Ribbon page allows you to delete the selected file system modification from the project Copy To The Copy To button from the Management group on the File System contextual Ribbon page should be used to copy the selected

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/file-system-modifications (2016-05-01)
    Open archived version from archive

  • Registry Modifications - MSI Package Builder
    between the Create Modify and Delete operations While specifying registry modifications you can provide a path to the Name field the missing path elements will be automatically created in the registry modifications The Name field supports the property definition placeholders so you can use the standard MSI properties while specifying the arguments See the Property Definition Placeholders section of this document for the list of available placeholders It is also possible to specify if the registry key should be treated as persistent thus not removed during an MSI package uninstall process within the Advanced Options group The advanced options are provided for the experienced users Please do not modify these options until you are absolutely sure that this modification is required for the correct package deployment To add a new registry value modification select the key you want to add modification to and choose the appropriate value type from the New item in the pop up menu or from the drop down of the Value button from the New group on the Registry contextual Ribbon page The New Value dialog will appear on the screen This dialog is almost the same for all value types it differs only with a value data editor Pic 3 Adding a registry value modification to a project While configuring a registry value modification you should specify a value name and an operation to be performed over this value during an MSI package deployment You can choose between Create Modify and Delete operations For the value creation and modification you can define a data to be written to this value For the string expandable string and multi string values in case if the value already exists you can choose if it should be overridden by the specified data or the specified data should be appended prepended to the existing To define a modification to a default registry value you can select it and choose the Edit item from the pop up menu If you want to edit it as a type different from REG SZ you should use the Change Type item from the pop up menu It is also possible to specify if the registry value should be treated as persistent thus not removed during an MSI package uninstall process within the Advanced Options group The advanced options are provided for the experienced users Please do not modify these options until you are absolutely sure that this modification is required for the correct package deployment The Value Name and Value Data fields support the property definition placeholders so you can use the standard MSI properties while specifying the arguments See the Property Definition Placeholders section of this document for the list of available placeholders Edit The Edit button from the Management group on the Registry contextual Ribbon page should be used to change the selected registry modification Delete The Delete button from the Management group on the Registry contextual Ribbon page allows you to delete the selected registry modification from the selected project Copy

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/registry-modifications (2016-05-01)
    Open archived version from archive

  • Environment Variables Modifications - MSI Package Builder
    can choose between the Create Create if does not exist Remove and Remove if value equals operations For creating an environment variable you should provide a variable value to the Value field If variable already exists during a generated package installation you can choose if its value should be overridden with the defined one or the defined value should be appended prepended to the existing one The System Variable checkbox is used to identify if you are going to modify system or user environment variable It is also possible to specify if the environment variable should be treated as persistent thus not removed during an MSI package uninstall process within the Advanced Options group The advanced options are provided for the experienced users Please do not modify these options until you are absolutely sure that this modification is required for the correct package deployment The Value field supports the property definition placeholders so you can use the standard MSI properties while specifying the value for an environment variable See the Property Definition Placeholders section of this document for the list of available placeholders Edit The Edit button from the Management group on the Environment Variables contextual Ribbon page should be used to change the selected environment variables modification Delete The Delete button from the Management group on the Environment Variables contextual Ribbon page allows you to delete the selected environment variables modifications from the selected project Copy To The Copy To button from the Management group on the Environment Variables contextual Ribbon page should be used to copy the selected environment variables modifications to another location Move To The Move To button from the Management group on the Environment Variables contextual Ribbon page allows you to move the selected environment variables modifications to another location The environment variables modifications can

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/environment-variables-modifications (2016-05-01)
    Open archived version from archive



  •