YUP its working... thanks dear for pointing to rihgt direction...
Cheers
Francis Kam wrote:
>
> Using a wxi should work.
>
> -Francis
>
>
>
> On Tue, Sep 16, 2008 at 10:20 AM, BOB1981
> <[EMAIL PROTECTED]>wrote:
>
>>
>> Hi Fracis,
>>
>> Another IDEA, Do you think putting the Custom Actions
Using a wxi should work.
-Francis
On Tue, Sep 16, 2008 at 10:20 AM, BOB1981 <[EMAIL PROTECTED]>wrote:
>
> Hi Fracis,
>
> Another IDEA, Do you think putting the Custom Actions and
> InstallExecuteSequence in a element rather then Fragment would
> work and create a wxi file rather then wxs and
Hi Fracis,
Another IDEA, Do you think putting the Custom Actions and
InstallExecuteSequence in a element rather then Fragment would
work and create a wxi file rather then wxs and using include to add it into
the product.wxs
something like this...
i actually have`t done this before, could a
Hi Fracis,
as you know the Fragment is generated on the fly so as the custom actions
and there id`s.
So how can i ref the Custom action in product.wxs when the ID``s are
generated on the FLY.
Thanks
Francis Kam wrote:
>
> Product.wxs has to reference the fragment somehow or another for it to
Product.wxs has to reference the fragment somehow or another for it to get
picked up. Assuming that only the contents of the CA are generated on the
fly (i.e. you know the names beforehand) one way to do this is to use the
CustomActionRef element in your Product.wxs.
-Francis
On Tue, Sep 16, 20
Hi All,
I am generating this Wxs Fragment file and compiling it with my Product.wxs
, it compiles and generates MSI package with no errors or warnings But when
i run MSI and install/Uninstall the Features these custom actions are Not
running At All,
Then i thought to Run DARK against my MSI gen
6 matches
Mail list logo
