Re: [WiX-users] CustomAction that needs to figure out the destination path

2011-04-28 Thread Bob Arnson
On 27-Apr-11 03:06, Rune Moberg wrote: > A little googling seems to suggest that the proper way to do this > would be by using a deferred action. If I understand this correctly, > the deferred action will be executed by the installer service and has > a good chance of running elevated. Fine, except

Re: [WiX-users] CustomAction that needs to figure out the destination path

2011-04-27 Thread Rune Moberg
On Mon, Apr 25, 2011 at 1:56 AM, Bob Arnson wrote: > Deferred custom actions can only get a couple of system properties. To > get any other properties (public or not), you need an immediate CA that > writes CustomActionData for the deferred CA. Funnily enough, this played straight into what I am

Re: [WiX-users] CustomAction that needs to figure out the destination path

2011-04-26 Thread Rune Moberg
On Tue, Apr 26, 2011 at 6:26 AM, Blair wrote: > Depends on when your custom action is scheduled. Can you describe in more > detail what you are trying to achieve? My installer installs an empty database. On upgrade, I need to call a stored procedure on said database. My plan was to have a custom

Re: [WiX-users] CustomAction that needs to figure out the destination path

2011-04-25 Thread Blair
: [WiX-users] CustomAction that needs to figure out the destination path Given a feature or a component (or for that matter a file), what is the best way for my custom action to determine the destination folder? Do I have to drill down into the Directory table and build the full path myself, or is

Re: [WiX-users] CustomAction that needs to figure out the destination path

2011-04-24 Thread Bob Arnson
On 23-Apr-11 20:33, Aaron Klor wrote: > a similar manner. If the CA is deferred, (again, unless I'm mistaken) you'll > only have access public properties (directory ids and such defined in > ALLCAPS), but you should be able to get the paths you need. Deferred custom actions can only get a couple o

Re: [WiX-users] CustomAction that needs to figure out the destination path

2011-04-23 Thread Aaron Klor
Unless I misunderstand your question, you should be able to get it easily by using [directoryid] (e.g. the ConfigurableDirectory of the feature) or [#fileid] as input parameters to your CA. From within an immediate custom action, you should be able to read the properties from the session object in

[WiX-users] CustomAction that needs to figure out the destination path

2011-04-23 Thread Rune Moberg
Given a feature or a component (or for that matter a file), what is the best way for my custom action to determine the destination folder? Do I have to drill down into the Directory table and build the full path myself, or is there an easier way? TIA. -- Rune --