Is it a case of all or nothing though? I didn't think the examples I listed above were too crazy...
On Thu, May 20, 2010 at 12:43 PM, Garrett Serack <garre...@microsoft.com>wrote: > No. > > > > If there are custom actions that need supporting they are going to have to > be added to what CoApp supports. > > > > Custom Actions are one of the worst parts and most abused features in MSI. > > > > > > > > *From:* coapp-developers-bounces+garretts=microsoft.com@ > lists.launchpad.net > [mailto:coapp-developers-bounces+garretts<coapp-developers-bounces%2Bgarretts> > =microsoft....@lists.launchpad.net] *On Behalf Of *Adam Baxter > *Sent:* Wednesday, May 19, 2010 7:30 PM > *To:* coapp-developers@lists.launchpad.net > *Subject:* [Coapp-developers] [specs] Pre and post install actions? > > > > Hi, > > Do you think each package type should have pre and post install actions? > > > > For example, > > * an executable package might register itself to the Games Explorer on > Vista/7 after installation > > * a source package might need a very specific folder structure > > * an executable might require non-CoApp resources to run, for example an > activation key or data files from a CD (think a free application with > non-free addons) > > * a package that is saving some configuration details to the registry (not > recommended, limits portable installations) > > and so on > > > > If so, what would be the best way to document this? I was just going to add > a "Pre & Post Install" section to each package blueprint. > > > > --Adam >
_______________________________________________ Mailing list: https://launchpad.net/~coapp-developers Post to : coapp-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~coapp-developers More help : https://help.launchpad.net/ListHelp
