![]() ![]() StrFilePath = wshShell.ExpandEnvironmentStrings("%ProgramFiles(x86)%") & Session.Property("Manufacturer") & "\" & Session.Property("ProductName") & "\config.xml" Set wshShell = CreateObject( "WScript.Shell" ) Butįirst, let's review a scenario of how Deferred CustomActions behave. Properties from Deferred CustomActions by using CustomActionData. This is the reason why the information about the original session handleĪnd property data is not available to a Deferredįurther on, we will go through how to access these installer Script generated for them is executed outside the installation session. When using Deferred CustomActions, you should note that the However, accessing Windows Installer properties within aĭeferred CustomAction doesn't work the same as with ImmediateĬustomActions (using Session.Property). Is usually parsed to a Deferred CustomAction. Information for the installation and when I do, the information gathered ![]() Only from time to time, I need to create a CustomAction to gather System (like adding, deleting or updating a file or a registry key). This is due to the fact that I often need to make coreĬhanges to install and configure an application meant to modify the Why do you need CustomActionData to Access Windows InstallerĪs an Application Packager, I hardly ever use ImmediateĬustomActions. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |