inno script studio make install visible to all users

#INNO SCRIPT STUDIO MAKE INSTALL VISIBLE TO ALL USERS HOW TO#
#INNO SCRIPT STUDIO MAKE INSTALL VISIBLE TO ALL USERS FULL#

One caveat: Anti-virus software sometimes intercepts VBScript code and could prevent your custom action from working properly. Square brackets indicate that the actual value will be resolved at run time. So angle brackets are used for passing multiple property values into a custom action. Since angle brackets are not allowed in file names, they can serve as separators for parsing the combined properties and separating them out.

#INNO SCRIPT STUDIO MAKE INSTALL VISIBLE TO ALL USERS FULL#

TARGETDIR is the primary installation folder, OriginalDatabase is the full path to the current MSI file being installed, and ComputerName is the name of the computer. The data consists of three Windows Installer properties. That is, you’re passing this data indirectly via the CustomActionData property. You’re passing the value of this string to the CustomActionData property, and then in the custom-action code you get the value from the CustomActionData property. This custom-action script will display the value of the CustomActionData property: We’ll illustrate this CustomActionData idea with a simple VBScript custom action. Remember that the properties can be standard Windows Installer properties (TARGETDIR, VersionNT and so on), or properties that you created yourself, perhaps by using Search Target Machine as we saw in the previous article.

This is a common theme in the examples that follow. To pass data into your custom-action code in Visual Studio setup projects, for example, you set the CustomActionData property to the data you want to pass into the custom action, and in your code you retrieve the CustomActionData property that contains the data.

#INNO SCRIPT STUDIO MAKE INSTALL VISIBLE TO ALL USERS HOW TO#

To understand the use of custom actions, it’s important to know how to use Windows Installer properties, and in particular the CustomActionData property. (You can download the code examples to go with this article using the link to the right of the title.) Properties and CustomActionData

Examples of standard actions include copying files and registering COM servers. Custom actions are in contrast to the standard actions that Windows Installer performs during an installation. It’s often necessary to add your own code to a Visual Studio setup project, which is accomplished using custom actions. This article describes the kinds of custom actions that can be used in your Visual Studio setup project. Second in a series on Visual Studio setup.

Inno script studio make install visible to all users