By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies. Summary AdminStudio WiseScript Package Editor is an application development tool that enables you to create and edit installation packages that are built with the WiseScript scripting language.
Synopsis AdminStudio WiseScript Package Editor is an application development tool that enables you to create and edit installation packages that are built with the WiseScript scripting language. Use WiseScript Package Editor to edit and refine installations that you have imported from legacy installations, or that you have re-created with SetupCapture or ApplicationWatch.
Asked 13 years ago views. Posted by: reds4eva 13 years ago. Im in Nigeria. Another post which belongs in the 'Scripting' forum Posted by: pgiesbergen 13 years ago. It needs an SMS server to unpack, but you can trick the setup by adding a registry key somewhere cant remember which one exactly Don't you love MS security?
Posted by: bkelly 13 years ago. Have a look at AutoIt. It is a free scripting language developed to help automate installations and the like. It does not use GUI dialogs like WiseScript does, but it is fairly simple to understand to the extend that it really does not need one.
This isn't free though at least not after the 45 day trial is over. Posted by: yumchild 13 years ago. EXEs to use as custom actions in Windows Installer installations. These custom actions can extend the capabilities of Microsoft Windows Installer and simplify installation tasks example: parsing and arithmetic functions that are difficult to accomplish with Windows Installer.
WiseScript Package Editor Reference 12 Introduction WiseScript Benefits WiseScript is a high-level scripting language that consolidates dozens or hundreds of lines of code into predefined script actions. The script author is prompted for the parameters needed by each script action, so a script can be created and tested very quickly. The script is displayed in clear, English-like statements. No runtime needed WiseScripts are compiled into self-contained. EXEs that do not require an agent or runtime files on the destination computer.
Compact size A WiseScript. EXE is small in size about KB. If a script uses any files that may not be on the destination computer, it can compress those files into the.
Example: A script that detects and removes spyware might temporarily install Kill. Built-in rollback WiseScripts can be rolled back after they are executed on the destination computer. User interface WiseScripts can incorporate any type of dialog box to either inform the end user or prompt for input. WiseScript is extensible You can streamline your scripting process by creating your own script actions for tasks that you perform frequently. To create a user-defined action, create a WiseScript.
Your action will be available for use in future scripts. WiseScript Examples In addition to creating installation packages, following are just a few of the tasks you can accomplish with WiseScript. Move files and directories. Modify a machine resource example: registry key or. INI file. Locate and delete a file and its directory example: to remove a spyware program.
Find the current Windows version. Find and report system information and take action depending on the results. Map a network drive. Assign license numbers from a text file. Getting Started Following is a broad outline of possible steps for building and distributing an installation: 1. Create a new installation or WiseScript. See Starting the Software on page WiseScript Package Editor only Set options on the Installation Expert pages to create basic installation functionality.
See About Installation Expert on page Edit the script in Script Editor to create advanced installation functionality. Create or customize dialog boxes. See About Dialog Boxes on page Test and debug the installation. WiseScript Package Editor only Explore options for outputting the installation. EXE file and prepare it for distribution. See Media on page 61 and WebDeploy on page To create a compiled.
EXE, click Compile. Use the Package Distribution tool to distribute the installation. This lets you create WiseScripts for Windows Installer custom actions. To open an existing script, select Edit Existing WiseScript from the button menu. You can begin to add or edit script actions. For information on adding script actions, see Adding an Action to a Script on page For a description of each script action, see About WiseScript Actions on page This lets you create WiseScripts that can be used alone or within a Windows Installer custom action.
The installation associated with the current project might open by default. This tool might open to a different view based on command-line options defined in Process Templates Setup. The New Installation File dialog box appears. Select one of the following: Empty Project Create an installation project file based on the Empty Project.
It contains a default script in which the basic elements of an installation are already configured. Project files do not store the files you add to an installation but the paths to the files. If you move the source files, the paths break. For information on how to fix broken paths, see Changing Source Directories on page Blank Script Build an installation or custom.
EXE entirely in Script Editor. If you select this, some pages in Installation Expert are not available. Click OK. The installation opens, and you can edit it in Installation Expert or Script Editor. IPF and edit them just as you edit. WSE files. The Open dialog box appears. Specify the. IPF file. The installation script appears in Script Editor. Edit and compile the file in the same manner as a. WSE file. See About the Project Settings View on page Installation Expert WiseScript Package Editor only Installation Expert lets you build an installation by pointing and clicking to fill out options.
See Using Installation Expert on page See About Script Editor on page Script Editor lets you develop more complex installations. Also use it to create powerful. EXEs to use as custom actions in a Windows Installer installation. To navigate between views, click the navigation tabs at the lower left of the main window. The Installation Expert and Script Editor views are interrelated.
As you build an installation using Installation Expert, a script is also created in Script Editor. Example: When you add a new file to the installation using Installation Expert, a line appears in the script with installation instructions for that file. When the installation is run, the script installs the file. Click Yes to delete your custom code, or No to preserve it. If you click No, you have access to a limited set of pages in Installation Expert.
This message appears if you create a custom script in Script Editor, then try to switch to Installation Expert. Click No to preserve the custom script. You are trying to open an installation in Installation Expert, which is not compatible with some custom scripts, so the script will be opened in Script Editor instead. This message appears if you open a custom script while in Installation Expert view. When Installation Expert opens, only the pages that do not affect the script appear.
Additional Interfaces The Tools menu offers specialized tools with which you can start an installation script. The Compile, Test, Debug, and Run buttons let you test and compile the installation.
MSI format. Therefore, it can provide only those capabilities that are provided by the Windows Installer SDK environment. WiseScript Package Editor provides an additional authoring environment that has a larger selection of more versatile script actions than those provided by Windows Installer products.
You can use WiseScript-based. EXEs in the same way that you use functions in. You write the main installation in a Windows Installer product, but when you need to perform an advanced function, you can create a WiseScript.
EXE and call it with a custom action in the Windows Installer installation. Creating a WiseScript. EXE has some advantages over writing a custom program to create an. EXE: WiseScript Editor uses predefined, easy-to-use script actions to accomplish common installation tasks.
You can pass Windows Installer properties in and out of the WiseScript. You can evaluate Windows Installer conditions within a WiseScript. See Evaluate Windows Installer Condition on page The disadvantage of using a WiseScript. EXE example: installation of a file.
If you use a WiseScript. EXE in a Windows Installer installation that will run on Windows Vista, you must specify a manifest file that indicates the run level for the.
See Using the Debug Commands on page Compile Click Compile to build a single executable file that contains the installation script as well as all the files needed for the installation. This is the installation. EXE that you distribute to end users. If any files are absent or not readable, error messages appear when compiling.
In WiseScript Package Editor, the installation is saved each time you compile unless you mark the Prompt to Save check box in Preferences. See Setting Preferences on page Test Click Test to compile and run the installation in test mode. In test mode, the installation performs all script actions without actually installing or modifying files.
However, if any script lines are dependent on files being installed by previous script lines, then test mode might fail. Run Click Run to execute the installation just as it would execute on the destination computer. Files are installed on your computer and your system is modified. Creating a Portable Project You can create a portable WiseScript project that contains all of the files in a WiseScript including its source files. A portable project is a self-extracting.
Use it to: Easily move WiseScript projects from one computer to another without having to copy source files. Share WiseScript projects with others, who can then open and edit your WiseScript with all of its source files.
To create a portable project 1. When the portable project. If you have modified these scripts and they are included in the WiseScript, then you should include them in the project Password protect the project package To add password protection to the project, mark this option and then enter and confirm the password. The Save As dialog box appears.
Specify the file name and location for the portable WiseScript project and click Save. See Creating and Editing Installation Templates on page Change the page groups by either selecting a pre-defined view of page groups or creating your own view. Change prompts and error messages displayed by the installation. See Editing Installation Messages on page Set preferences.
Set the actions list in Script Editor to display only those actions you use most frequently and add your own actions to the list. Change the dialog boxes that display during installation by editing default dialog boxes. See Editing Dialog Box Templates on page Templates contain logical defaults and commonly used settings. Some template files are predefined and appear when you create a new installation.
You also can create your own templates. Examples: If all your installations have the same system configuration requirements and document file extensions, you can create a template with these changes preconfigured.
If your installations require a language that is not pre-translated, you can add translated custom dialog boxes to a template to make the dialog box translations available to future installations. Warning Editing predefined templates is not recommended, because they might be overwritten during upgrades. Instead, save customized templates with different names, or make copies of the predefined templates and edit the copies. To create a custom template 1.
Select Empty Project and click OK. Make all the changes that should appear in installations that will be created with this template. Save the file: a. Name the file and save it in the Template directory as a. The New Installation File dialog box appears and includes the template you just created. If the New Installation File dialog box does not contain the new template, verify that you saved it in the Templates directory.
Select the template you just created and click OK. Verify that the changes you made in the template are present in this new installation. From the Pages menu, you can select one of the following page groups: All Displays all page groups and all pages associated with each group.
Properties Displays only the pages that do not add or change script lines in the script. You can add page groups to the Pages menu. This lets you customize your work environment so you only see the pages you frequently use. You can edit any set of page groups you create, but not the predefined sets. You also cannot edit page names. To add a page group 1.
The Customize Pages dialog box appears. On the dialog box that appears, specify a name for the new set of page groups. The name appears in the Name drop-down list. To add a new page group, click the Add button on the left and specify a name for the page group. The name appears in the Page Groups list.
To add a page to a page group, select the page group, and click the Add button on the right. The Select Pages to Add dialog box appears. Buttons to edit page groups and pages are unavailable when a predefined page view is selected in Name. These pages appear under the group selected in Page Groups. The page groups appear on the left side of Installation Expert. Select the page or pages and click OK. Add more page groups and pages as appropriate.
Your new set of page groups appears under the Pages menu. Editing Installation Messages WiseScript Package Editor only You can edit the prompts and error messages that are displayed by an installation. Installation messages are stored in wise. Changes that you make to installation messages become available to all installations.
To back up the installation messages before editing them, back up wise. When you add multiple-language support to an installation, you can edit or add installation messages in languages other than English. Messages are provided for the following pre-translated languages: English, French, German, Italian, and Spanish.
To add support for any other language, obtain translations of the message text and enter the translated strings on the Installer Messages dialog box. For information on adding language support to an installation, see Language Support on page To edit installation messages 1.
The Installer Messages dialog box appears. Complete the dialog box: Language Name Select the language for which you will edit messages. Translated Name The name of the language as it will appear in installations that you create.
See Windows Language Codes on page Messages Select the message to edit. You can edit as many of the messages as necessary. Message Text Enter or edit the message. If you select a language that is not predefined, the messages are in English. Select Language Dialog When end users run an installation that supports multiple languages, the Select Language dialog box appears first, where they select a language.
Changes that you make in these fields apply to all languages. Dialog Text This text appears on the Select Language dialog box. If the installation supports multiple languages, enter instructions in all supported languages.
Also specify. Complete the Preferences dialog box: Prompt to Save Mark this to have Script Editor prompt you to save the installation script each time you build a new installation.
If you do not mark this check box, the script is always saved before compiling. Compiler variables are set on the Compiler Variables page. Add Associated Icons and Registry Keys If you mark this, when you add a file on the Files page in Installation Expert, icons and registry keys that are associated with that file are added also.
Append New Script Lines If you mark this, when you add a new script action in Script Editor, it is inserted after the currently selected script line, rather than before.
Listbox Compatible Mode If your computer has certain video drivers, you might have problems selecting items from list boxes within WiseScript Package Editor. If items you select from list boxes are continually misinterpreted, mark this check box to eliminate list box problems. The backup file name consists of the current file name plus a number.
Example: If the current file name is Application. Use caution with this option because a new file is created every time you save. Color Selection Select the colors for the types of script actions recognized by Script Editor. Select the type of script action and then click Set Color to select the color.
Suppress Version Error Mark this to suppress errors that normally occur when version checking is performed on files that do not have version resources. Background Processing Mark this to allow other applications to run during compile.
If this is cleared, user input is ignored during compile. Smart Create Mark this to compile the installation. EXE whenever any file in the installation changes.
If this is marked, the time you wait after clicking the Run button increases slightly because the compiler checks the modified dates and sizes of all files in the installation to determine if they have changed. Mark this check box only when testing and clear it for the final build.
Fast Create Mark this to speed compiling by copying the compressed version of a file from the previous version of the installation. EXE to the new one. If the size or date of a file has changed, it is recompressed. Run in Manual Mode Mark this to have the installation. EXE prompt for the locations of all directories to be used for installations example: Windows, System, and so on whenever the installation is run from within WiseScript Package Editor.
Use this field to specify an additional directory to hold user- defined actions. This can be a local or shared network directory. The actions stored in this directory appear in the Actions list in Script Editor in addition to the ones in the Actions directory.
DLLs to Exclude Enter the names of. DLL and. OCX files that should not be included when you create a. Enter one file name on each line with no other delimiter. DLL because that file is accessed by Visual Basic applications, but is not necessarily installed with the Visual Basic application. Downloading Application Runtimes WiseScript Package Editor only The Download Runtimes wizard provides an easy way to get runtime files or runtime installations that you plan to deploy with your application.
You can also use this wizard to download updates to runtimes you currently have. The runtime versions are free, and you can download as many as you need.
To download application runtimes 1. Connect to the Internet. The Check for Updates page appears. Click Next on the Check for Updates page. The Select Runtimes page appears. This lists the runtimes you currently have installed, and lists all the runtimes that are available for downloading. On the Select Runtime page, mark the check box for each runtime you want to download. You can click Select All to select all the runtimes, or click Clear All to clear your selections. As you mark check boxes, the Download Size field displays the total size of the files you selected.
When you finish selecting runtimes, click Next. The Start Update Download page appears. Click Next to begin the download. The selected runtime updates are downloaded from the Internet and installed in the appropriate Wise runtime directory.
When the download is finished, the Update Complete page appears. Click Finish. WiseScript Package Editor only As you work on an installation, paths to files in the installation can become note valid if you: Move files that are part of the installation to a new directory on your computer or network. Move the installation file itself from your computer to another computer. Use relative paths and then move the installation file.
Rename a directory. If the paths are not valid, then during compile, error messages warn that files cannot be opened. Rather than adding the files again, you can specify the new source directories for these files.
The Change Source Directories dialog box appears and lists all the directories referenced in the script. Select a directory in the list. Developer's Description By Altiris. Take advantage of the benefits of application virtualization by using Wise Package Studio to create packages that configure virtual applications. You can also edit virtual packages using the Virtual Package Editor and manage them using Software Manager. Full Specifications. What's new in version 7. Date Added November 28, Version 7.
Operating Systems. Additional Requirements None. Total Downloads 14, Downloads Last Week 6. Report Software.
0コメント