Hi Bob,
thanks for reply.
What I discovered seems to meet, what you are writing. I can't interrupt
AppSearch with a custom action.
Thats the point where I started thinking about a WixExtension.
What I like to do is some kind of (imagine all xx are valid values):
<Property Id='REGISTRY_SEARCH_RESULT'>
<RegistrySearch Id='xx' Root='xx' Key='xx' Type'raw'/>
</Property>
<Property Id='DIRECTORY_SEARCH_RESULT'>
<DirectorySearch Id='xx' AssingToProperty='yes'
Path='$(manipulate([REGISTRY_SEARCH_RESULT])'/>
</Property>
So that the path provided for the directory search is adjusted in the
maipulate function of an extension. I have to do this, because I'll get
'Some/Path/To/Executable.exe -param' from the registry search but I only
need the part 'Some/Path/To' in the directory search.
Is there a way to do this at all?
Regards, Michel
Am 03.06.2012 19:13, schrieb Bob Arnson:
> On 01-Jun-12 10:09, Michael Scheepers wrote:
>> Now I think a small extension is what I need, but I am not sure if the
>> extension is packaged to the msi or is only used at compile time (when
>> calling candle / light) or also at runtime when it is required.
> It can be both but nothing will allow you to add behavior to built-in
> MSI functionality. You can't interrupt AppSearch with a custom action.
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
