Update Tables in WISE Using VBScript | CodeGuru

Update Tables in WISE Using VBScript

The WISE application is used to generate installation kits. Using WISE, the user can select files from the local machine and add them to the installation. By adding a file to the installation, WISE saves its location on the local machine. For example: We want to install an INI file that is located under: C:\Program […]

Written By
CodeGuru Staff
CodeGuru Staff
Aug 12, 2004
2 minute read
CodeGuru content and product recommendations are editorially independent. We may make money when you click on links to our partners. Learn More

The WISE application is used to generate installation kits. Using WISE, the user can select files from the local machine and add them to the installation. By adding a file to the installation, WISE saves its location on the local machine.

For example: We want to install an INI file that is located under: C:\Program Files\MyProgram\Ini Files.

What happens if we want to generate an installation, using the same INI file, but taken from other location on the local machine? We would have to enter WISE and manually change the file by selecting it from the new location and compile.

It’s easy when there is only one file, but what happens if we have hundreds of files like that?

The example is relevant for developers who develop on a multiple projects environment: We have three projects: AAA, BBB, and CCC. All have the same installations, using the same files, taken from different locations:

The DLLs and EXEs of project AAA are saved under C:\VssWorkingFolder\Projects\Release\AAA.

The DLLs and EXEs of project BBB are saved under C:\VssWorkingFolder\Projects\Release\BBB.

The DLLs and EXEs of project CCC are saved under C:\VssWorkingFolder\Projects\Release\CCC.

Using the manual way, we will have to change the WISE script manually (change the path of all the files) for each project and compile it.

This article shows you an easier way:

  1. Under the ‘Setup Editor’ tab, under Tables: In the Property table add a row: Property = RELEASE_DIR. Value = C:\.
  2. Under the ‘MSI Script’ tab, under ‘User Interface’ tab, search the line containing ‘MigrateFeatureStates’. Under this line, add a custom action: ‘Call VBScript From Installation’.

  3. In the dialog box, insert the relevant details: for ‘Custom Action Name’ enter whatever you want. For ‘Script File,’ enter the name of the VBScript file.

    For ‘Script Function Call: enter the name of the function, as written in the VBScript: UpdateProperty.

  4. The script is attached.
  5. In case you wish to convert paths: use the ‘Tools > Convert Source Paths’ menu option. This dialog displays all the paths of the files that take part in the installation.
  6. Press the ‘Change Selected Path’ button, and in the ‘Change To’ edit box, enter the property surrounded with [ ].
  7. Press OK. The ‘Convert Source Paths’ will display the paths as properties.

Now, to create the installation script for the AAA Project, change the VBScript: C:\VssWorkingFolder\Projects\Release\AAA. To create the installation script for the BBB Project, change the VBScript: C:\VssWorkingFolder\Projects\Release\BBB. To create the installation script for the CCC Project, change the VBScript: C:\VssWorkingFolder\Projects\Release\CCC.

That way, you need to change in only one location. Don’t forget to compile the WISE script after changing the VBScript.

CodeGuru Logo

CodeGuru covers topics related to Microsoft-related software development, mobile development, database management, and web application programming. In addition to tutorials and how-tos that teach programmers how to code in Microsoft-related languages and frameworks like C# and .Net, we also publish articles on software development tools, the latest in developer news, and advice for project managers. Cloud services such as Microsoft Azure and database options including SQL Server and MSSQL are also frequently covered.

Property of TechnologyAdvice. © 2026 TechnologyAdvice. All Rights Reserved

Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.