I'm not sure if this is as-designed or not, but it turns out the problem
was in having multiple fragments in the wixlib source, and no reference
between the fragments. 

 

This doesn't include the CustomAction or InstallExecuteSequence updates,
but it does include the Component and ComponentGroup information:

<?xml version="1.0" encoding="utf-8"?>

<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";>

    <Fragment>

        <ComponentGroup Id="SharedThing">

            <ComponentRef Id="SharedThing.dll" />

        </ComponentGroup>

    </Fragment>

    <Fragment>

        <DirectoryRef Id="INSTALLDIR_SHAREDTHING">

            <Component Id="SharedThing.dll"
Guid="{371532AB-D86F-4283-BD69-0583BD67E356}">

                <File Id="SharedThing.dll" KeyPath="yes"
Source="C:\Projects\_Binaries\SharedThing.dll" />

            </Component>

        </DirectoryRef>

    </Fragment>

    <Fragment>

        <CustomAction Id="SetAProperty" Property="AProperty"
Value="TheValue" />

        <InstallExecuteSequence>

            <Custom Action="SetAProperty"
After="CostFinalize">1</Custom>

        </InstallExecuteSequence>

    </Fragment>

 

</Wix>

 

This includes everything:

<?xml version="1.0" encoding="utf-8"?>

<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";>

    <Fragment>

        <ComponentGroup Id="SharedThing">

            <ComponentRef Id="SharedThing.dll" />

        </ComponentGroup>

        <DirectoryRef Id="INSTALLDIR_SHAREDTHING">

            <Component Id="SharedThing.dll"
Guid="{371532AB-D86F-4283-BD69-0583BD67E356}">

                <File Id="SharedThing.dll" KeyPath="yes"
Source="C:\Projects\_Binaries\SharedThing.dll" />

            </Component>

        </DirectoryRef>

        <CustomAction Id="SetAProperty" Property="AProperty"
Value="TheValue" />

        <InstallExecuteSequence>

            <Custom Action="SetAProperty"
After="CostFinalize">1</Custom>

        </InstallExecuteSequence>

    </Fragment>

</Wix>

 

>Can you share out an example of how the elements are organized in
Fragments?

>Most likely you're just needing a reference that isn't in place.

> 

>On Tue, Dec 22, 2009 at 3:33 PM, <eric.hyb...@emc.com> wrote:

> 

>> I defined some components and custom actions and use those custom

>> actions in the InstallExecute sequence within a Fragment. When I
create

>> a wixlib (with lit.exe) from that Fragment and include the .wixlib
with

>> my primary msi light command line, I get the components, but not the

>> custom actions or the references to those custom actions in the

>> InstallExecute sequence. I don't get any errors during any portion of

>> the process. I do see the expected information in the wixlib if I
open

>> it with an editor and poke around within the file.

>> 

>> Can someone provide a sample or suggestions, since I'm clearly
missing

>> something obvious?

>> 

>> Thanks,

>> 

>> e

 

 

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to