Ah, that makes more sense. Thanks. On Thu, May 20, 2010 at 12:46 PM, Adam Kennedy <adamkennedybac...@gmail.com>wrote:
> Off the top of my head... > > WiX already has elements in it to add something to the game explorer, > so it isn't an action. > > Likewise, folder structure isn't an action either. > > Activation keys are needed to run something, not install it, so the > app should really ask itself at first startup. > > Registry additions have WiX elements, it's not an action either. > > Adam K > > On 19 May 2010 22:29, Adam Baxter <volta...@voltagex.org> wrote: > > 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 > > > > >
_______________________________________________ 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
