thank you! that seems to answer my questions.
i'm using the double quotes and a set property action underneath the install button on the verify screens and i'm getting the expected results.
i'm having a similar issue on win2008. when should this property be set? are double quotes necessary? also if a previous version does not have this property set and that is being upgraded with a version that *does* have this property set, will the reboot be in fact suppressed?
i've tried to write the estimatedsize key out for products i already had on my development computer; but it doesn't seem to change the values shown in my list. do you have a recommended method to force this value that is displayed?
i have a set of 5 projects, Application Application (2) Application (3) Application (4) Application (5)
each with unique upgrade codes.
sometimes one or more products will install with accurate sizing reported in the programs control panel (about 60MB). sometimes the initial install reports zero ...
correct, is there an ETA for this fix? also can you reproduce the effect of not being able to uninstall a specific instance correctly? (i.e. it will remain in the programs control panel with a generic icon even after having said it uninstalled correctly)
i reproduced this behavior with the attached test projects.
install two instances of one version, then isntall an instance of another version, the instance dialog will only show one of the previous instances, not both.
does anyone know where i could get an ico file suitable for using with AI to mimic the VB messageboxicon.question graphic? i would like to use this image on some of my dialogs...
i think i may have it. for installs i leave off the last slash in my path that i provide to the installer, that runs. in repair (AI_MAINT) mode, i have a script check for the existence of a UNC path and strip the last character if so. trying to run this script check in AI_INSTALL mode mangles the ...
i am writing vbscript to check the appdir properties as published actiosn on the next install button of the verifyreadydlg in first time install and the repair button of the maintenancetypedlg; are there other or better locations or properties recommended for this type of checking?
during the install i have accounted for this behavior that only occurs on the usage of UNC path names by stripping the trailing slash and then observing AI ADDING a trailing slash. this behavior does not happen when using local or mapped drives during install (i.e. the path i provide has a trailing ...
on target directories that are UNC path values (for instance \\SERVER\Shared folder\) the installer adds an extra slash during install (AI_INSTALL) and during repair (AI_MAINT) so that i get an error that the path "\\SERVER\Shared folder\\" is not accessible. this is for a situation where a user is ...
FOLLOW US
Get the latest news in Application Packaging