Pete,
you posted
"Further investigation reveals the SHAREDADDINFOLDER Property isn't being used for anything I can see. Dropping that row from the Property table produces a working .msi and an AIR install that can use, install and run AIR apps. The installer creates and uses the folder set in the CustomAction table (SetSHAREDADDINFOLDER) fine after the Property table has been modified."
My question is how did you drop the row from the Property table to get that working MSI. I am trying to crate the adobe air msi so i can distribute it across the company and I am running into all kinds of issues when packaging it with WISE.
