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".
  • What's New in Version 4.0 - MSI Package Builder
    of file system resources during MSI creation This requirement caused by limitation for the path length of file system resources For each file system resource its path length including projects storage path shouldn t be more than 255 symbols Thus a short projects storage path is preferred for example C MSPBRoot Resolved issues This release resolves a number of issues the most important of which are listed below Wrong handling of multi string registry values with a special characters License key validation with a trailing newline characters Version 4 0 2 March 23 2008 Visual interface for services management Enterprise Edition now includes visual interface for services management Using this interface you can define services installation settings Improved MSI generation Generated MSI now supports more features from the list of standard MSI features set It means that these standard MSI features are preserved during decompilation and can be included into generated MSI without any change to keep similarity with original MSI Resolved issues This release resolves a number of issues the most important of which are listed below Rolling unrolling of registry values Set of visual defects labels controls alignment Controls enbling disabling in Preferences Slow MSI decompilation Wrong drag drop behaviour Potential access violation in MSI generation Wrong project preparation process in case of large data amount Version 4 0 November 30 2007 Services support in the Enterprise edition Starting from this version MSI Package Builder produce MSI packages which can install Windows services This feature allows to create customs MSI packages for original installations which include steps to install services At the current moment services support works in automatic mode only It means that during monitoring and decompilation services installation actions are detected and correspondent information is stored in the MSI Package Builder project and later used for

    Original URL path: http://emcosoftware.com/msi-package-builder/whats-new/4.0 (2016-05-01)
    Open archived version from archive


  • What's New in Version 3.3 - MSI Package Builder
    editions Application was split on three editions with different functionality and price If you don t need full range of MSI Package Builder features you can select edition with less functionality and save costs Starter Edition should be selected if you interested in manual MSI creation using truly visual MSI editor Professional Edition should be selected if you need to capture actions of existing installations and create custom MSI from monitoring results This edition also provides MSI decompilation feature Enterprise Edition should be selected if you need to use all MSI Package Builder features including environment variables changes during MSI installation Paste content from Windows clipboard If you need to include content of some folder into MSI project in addition to import options you can also use Copy Paste operations In this case all what you need is just to make a Copy to Windows clipboard in external tool Windows Explorer for example and then make Paste to the selected installation in Projects Tree or folder in File System Actions tree As the result folder with all its content will be added to the MSI project Drag Drop from external tools File system resources can be dragged to MSI Package Builder from external tools It s another way how to quickly create MSI content You can select folder in external tool like Windows Explorer for example and dragg it to installation in Projects Tree or folder in File System Actions tree As the result folder with all its content will be added to the MSI project Import from Registry Files reg MSI Package Builder allows registry changes importing into the project from Registry Files with reg extension represneted in REGEDIT4 or REGEDIT5 formats You can save a lot of time by registry data importing into MSI project instead of manual

    Original URL path: http://emcosoftware.com/msi-package-builder/whats-new/3.3 (2016-05-01)
    Open archived version from archive

  • What's New in Version 3.2 - MSI Package Builder
    3 2 March 21 2007 Windows Vista support MSI Package Builder become Windows Vista compatible You can perform monitoring MSI decompilation and all other actions on computers where Windows Vista is installed 64 bit Windows versions support A list of supported operation systems was supplemented by 64 bit platforms like Windows Vista x64 and Windows 2003 x64 MSI Package Builder was improved to work under these platforms System and user filters split All filters which can be configured in Options Preferences were split on two categories system and user System filters are preconfigured in MSI Package Builder and consists of known values which should be specially processed during MSI Package Builder work System filters set was created as a result of popular installations analysis System filters content can be changed during MSI Package Builder update in order to provide the most suitable default configuration If you want to have the own set of filters you can create it using user filters These filters will not be updated automatically Note that MSI Package Builder provides options for flexible filters tuning so you are able to enable or disable all system and user filters and also enable or disable any particular filter Resolved issues This release resolves a number of issues the most important of which are listed below Open file folder in Windows Explorer and open key in Regedit Logging during Roll Unroll operations Drag Drop operation Product Details Overview Advantages and Benefits Feature List What s New Testimonials Getting Started Downloads Purchase Documentation Screenshots Video Tour Requirements Main Features Create MSI Packages Build Silent MSI Packages Convert EXE to MSI Customize Existing Installations Product Facts Did you know that MSI Package Builder uses innovation technology that allows capturing installation data on the fly Did you know that Live Monitoring technology

    Original URL path: http://emcosoftware.com/msi-package-builder/whats-new/3.2 (2016-05-01)
    Open archived version from archive

  • What's New in Version 3.1 - MSI Package Builder
    installations using Ctrl or Shift key with mouse and then perform Delete Installations action from context or main menu Permanent files registry keys and values During application uninstallation not all installed resources can be simple deleted Some files and registry keys can be shared and used by few applications so shared resources deletion during the application uninstallation can cause inoperability of the rest applications You are able to define that file registry key or value should be permanent i e this resource will not be deleted during uninstallation You can set Do not remove this element during MSI package uninstall option in the Modify dialog by clicking on the Advanced button and switching dialog to the advanced mode Permanent filters In most cases you shouldn t care what files registry keys and values should be marked as permanent Permanent filters for file system and registry which are available through menu item Options Preferences Permanent Filters contain predefined set of file system path and registry keys which will be automatically marked as permanent during monitoring You can add delete or modify filter values or disable filtering Changes safety check MSI Package Builder performs project check in order to prevent MSI creation which can potentially affect Windows integrity and cause a system crash During project creation MSI Package Builder checks safety of all planned changes and shows warning icon for the resource which has unsafe operation It s just a warning which could be ignored but we recommend you take it seriously In the current version deletion of the system files and registry keys is checked Improved decompilation MSI packages decompilation was improved to extract information about files registry keys and values marked as permanent As a result MSI package generated by MSI Package Builder has the same permanent resources as original MSI File attributes support MSI Package Builder allows you to manage file attributes Read Only Hidden System Compresses for MSI resources After MSI installation file will have the same attributes as were set in MSI Package Builder Information about file attributes is represented by Attributes column on the File System tab You are able to change file attributes thought Modify File dialog by switching it to the Advanced mode MSI Package Builder is able to save information about a set of file attributes during monitoring and decompilation Later this information is used for MSI creation so after MSI installation files will have same properties as they had in original installation Environment variables support If monitored installation applies changes to environment variables the same changes are performed by MSI package created by MSI Package Builder Environment variables operations are handled correctly changes are applied during MSI installation and correctly rolled back during MSI uninstallation Navigation to resources Special actions Jump To Explorer and Jump To RegEdit were added for data on the File System and Registry tabs They are available either in the Edit menu or context menu Using this action you can see location of selected resource in file system

    Original URL path: http://emcosoftware.com/msi-package-builder/whats-new/3.1 (2016-05-01)
    Open archived version from archive

  • Getting to Know the Program Interface - MSI Package Builder
    wizard and you will see how to use the wizard in practice in the following chapters When the Repackage Installation wizard is closed and no MSI projects are opened you can see the starting main program screen The program has a Ribbon user interface so the Ribbon menu is displayed at the top of the screen providing you with an access to the main actions of the program Different types of the actions are located on different Ribbon tabs so you can switch them if required Additional Ribbon tabs are displayed automatically when specific elements are selected and provide you access to the contextual actions Under the Ribbon you can see opened projects on the left and the main area on the right When you start the program the Projects view is empty and the main area displays a list of the recent projects and the main actions of the program You can click the main actions to initiate the corresponding repackaging wizards You can open the Repackage Installation wizard to access all repackaging options by clicking Repackage Installation on the Ribbon Pic 1 The starting main screen If you have completed repackaging or opened previously created MSI projects you can see the current projects in the Projects view You can have more than one project opened to be able to copy data between the projects A project consists of different types of resources If you select a project node in the Projects view you can see and edit the project settings If you select for example the File System node you can review and modify files and folders in an MSI project using the file system editor There are different editors for managing different types of resources so you need to select the required item in the Projects tree

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/getting-to-know-the-program-interface (2016-05-01)
    Open archived version from archive

  • Overview of MSI Creation Methods - MSI Package Builder
    packages manually through visual editors by specifying the changes to be included into an MSI How to use these MSI creation methods in the program When you start the program for the first time the Repackage Installation wizard is displayed automatically In the Enterprise edition of the program as the first step you need to select if you would like to use monitoring or wrapping In the Professional edition you cannot use wrapping so you need to select the monitoring mode that will be described later in this chapter If you wish to create an MSI manually though editors you can close the wizard and create a new project using the Ribbon options Pic 1 Installation packaging options available in the Enterprise edition It is recommended to use monitoring in most cases since it is a universal method and wrapping or a manual MSI creation only if you have good reasons to do so Below you can find some examples demonstrating when using different types of the MSI creation methods makes sense Monitoring usage examples Repackage one or multiple non silent installations into a silent MSI Create a silent MSI package that includes a repackaged non silent installation and its customization the installed product registration configuration etc Create a custom silent MSI that includes any captured changes Wrapping usage examples Repackage an installation of a Windows component such as NET Framework for example that cannot be repackaged using monitoring The repackaged installation should support silent deployment Wrap one or multiple EXE MSI installations that can be deployed silently into a silent MSI Custom creation examples Create a simple MSI that deploys only a few resources Note that you can use monitoring not only for repackaging but also for creating custom installations by capturing the changes performed manually It is much easier to use that approach than to create an MSI manually using visual editors You can see how to use monitoring in practice in the Demos included in the Repackage EXE to MSI Using Monitoring and Create Customized Installations Using Monitoring chapters Wrapping is demonstrated in the Demo contained in the Repackage Silent Installations Using Wrapping chapter How to Select the Monitoring Mode You can use monitoring in a number of cases for instance to repackage single or multiple non silent installations to repackage a non silent installation and its customization or to create any custom installation To support all those cases monitoring can work in two modes which are Automated Monitoring and Advanced Monitoring that you can select in the Repackage Installation wizard Pic 2 Selecting the monitoring mode When you select any of the above modes EMCO MSI Package Builder uses the Live Monitoring technology to capture the file system and registry changes and create an MSI reproducing such changes You will learn how it works in the next chapter To understand which method you need to select you can review their comparison below Automated Monitoring Advanced Monitoring How repackaging works In the wizard you specify a non

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

  • Demo: Repackage Silent Installations Using Wrapping - MSI Package Builder
    installation file is executed with specific parameters Before generating an MSI package we need to ensure that the silent deployment of the original installation works as expected Use a virtual machine with a clean environment to test the silent installation of NET Framework which should be completed automatically while you should not be prompted to select any installation settings If the tested installation can be deployed silently you can proceed to the next step Step 2 Open the Repackage Installation wizard Run EMCO MSI Package Builder By default you should see the opened Repackage Installation wizard at the start of the program If it doesn t open automatically you may click the Repackage Installation button on the Home tab of the Ribbon Once the wizard is launched read the welcome information and press the Next button Step 3 Select the Wrap Installation option We are going to use installations wrapping so select the Wrap Installation option in the wizard and press the Next button to proceed to the next step Pic 1 Select the Wrap Installation option Step 4 Specify the installation file and the installation options You are prompted to enter the path to the installation In the file picker dialog specify the path to the NET Framework executable installation file You should specify the installation options in the New Wrapped Package dialog You can change the package name to NET Framework if you wish In this dialog you also need to specify the silent command line parameters to be passed to the installation As we know a NET Framework installation can be deployed silently when executed with the q norestart parameters so enter them into the Parameters field and press OK to close the dialog Finally press the Next button in the wizard to proceed to the next

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/demo-repackage-silent-installations-using-wrapping (2016-05-01)
    Open archived version from archive

  • Installation Project Editing and Customizing - MSI Package Builder
    MSI to be deployed as an update you only need to modify the MSI package properties First you need to modify the properties displayed in the Identification and Upgrade section Enable the Allow an installation upgrade option and specify the same Upgrade GUID as the one used in the MSI you wish to update You also need to update the Version number to ensure that the new MSI has a higher version number than the old one Learn more about the technical requirements for an upgrade in the How should I configure the repackaged installations to support an upgrade chapter Digitally Sign MSI Packages MSI packages apply Windows changes on deployment so Windows Installer requires that they should be run under an account with administrative permissions The Windows UAC automatically checks the validity of digital signatures when software is executed with administrative permissions By default MSI packages generated by EMCO MSI Package Builder aren t digitally signed so you can see the signature warning in the Windows UAC when you deploy such MSI packages manually If you need to deploy the generated MSI packages remotely note that such deployment tools as Microsoft SCCM don t deploy unsigned MSI packages EMCO MSI Package Builder allows signing MSI packages if you have a digital code signing certificate and specify it in the program Preferences dialog You can enable and disable digital signing of the generated MSI packages by configuring the corresponding options in the Digital Signature section of the MSI package properties You can learn more about digital MSI singing in the Signing MSI Packages chapter Review and Edit MSI Changes Under the project node in the Projects view you can find the list of changes applied by the installation These changes are grouped by types and are displayed as separate nodes in a tree so you can see File System Registry Assembles and Pre Post Actions The Enterprise edition of EMCO MSI Package Builder can modify an extended set of resources and includes Environment Variables Services Drivers and Wrapped Packages If you select a node on the right you can see a specific editor for the corresponding type of resources and can use it to review and modify the changes You can learn how to use every available editor in the MSI Projects chapter but here you can get a quick overview of the available features Pic 2 Editing File System changes If you select the File System node for example you can see the structure of folders on the left and the modified files on the right The resource icons shows the applied operation type so you can see the files that were created modified or deleted If you created an MSI project automatically using repackaging you can notice that the file system paths are not absolute and include so called System Folders This is required to make installations portable from one PC to another because different PCs may have different paths to standard Windows folders that store applications their

    Original URL path: http://emcosoftware.com/msi-package-builder/doc/installation-project-editing-and-customizing (2016-05-01)
    Open archived version from archive



  •