Although I have not used VBS custom actions in my projects, I assume they work same as any other custom action. Meaning, you do not have direct access to MSI properties in deferred custom actions. You have to pass the properties through the "Action Data" field. According to Microsoft's best practices, if you are making any system changes with this VBS file, it should be run as a deferred custom action.
It is important to note, this is not an Advanced Installer issue. It is the way MSI's are designed (very poor design in my opinion). Advanced Installer actually makes it easier to pass properties into deferred custom actions, by providing the "Action Data" field. In other tools (like InstallShield), you have to create a separate custom action to pass in properties (a lot messier).
Im always struggeling with the Standard Actions because I never know what habppens when. Is there an overview what the standard actions are doing?
I 100% agree with you on this. It's never been clear to me what it happening at any given point in the installation. Microsoft's documentation for Standard Actions is very shallow. I would also be interested in some documentation that provides in depth information on what exactly is happening in a given Standard Action.
http://wixtoolset.org provides some additional information on certain Standard Actions.
FOLLOW US
Get the latest news in Application Packaging