I have a project that creates a folder based off of a property. During maintenance -> modify I would like to give the option to change this folder location.
During CostFinalize the property value is always replaced to its original install value. I can force a property change after this event, but then if modify is ran again the value goes back to the initial installation directory (and not the last modified value).
Indeed, this is the default behaviour of Windows Installer. It does not support the concept of moving files from a location to another during the Maintenance.
By the way, can you please give us more details about your scenario?
The project is a maintenance system which will create custom database backups into a folder (outside of typical sql backups). The systems are installing on typically have a drive dedicated to similar functions (databases, backups, etc, etc) but not all. For a custom installation we want to be able to allow the customer to change the location of these backups, therefor we used a property based folder. Though this folder will not necessarily be linked to the installation location of the program itself, so we didn't make it a subfolder of appdir (which presumably is easier to change the location of).
It might be that a new location is more appropriate for these backups (another dedicated drive, or a different drive has relieved some space, whatever) so we wanted the location to be able to be modified.
I could create a custom action to create the folder and be able to change through a similar function, was just curious if the MSI would be able to do this naturally.
FOLLOW US
Get the latest news in Application Packaging