RE: [WiX-users] InstallExecuteSequence table does not contain InstallFiles and RemoveFiles entries

[Rob M. <ro...@us...>]

How are you building the Merge Modules?  If you are using the WiX toolset to
build the Merge Modules then you will see that WiX adds the necessary
actions to your Merge Module to ensure that when they get included in the
final MSI that the MSI has all the actions necessary for the Merge Modules
to succeed.

The Merge Module spec isn't really clear whether standard actions should
always be present in Merge Modules (my mistake from antiquity actually) but
it seems most tools (including the WiX toolset) do better when the standard
actions are included.  That is why the WiX toolset includes them.

If you are building the Merge Modules using a different tool (or consuming
Merge Modules built by a different tool) then it may be necessary to do as
you noted below and specifically add the necessary standard actions.  

It could be easily argued that WiX should automatically add the necessary
actions for you whether the Merge Modules include them or not.  The WiX
toolset does not at the moment, because WiX does not parse the Merge
Modules' tables itself.  Therefore, the WiX toolset doesn't exactly know
what actions your Merge Modules might need.


-----Original Message-----
From: wix...@li...
[mailto:wix...@li...] On Behalf Of Vitaly Dolya
Sent: Saturday, December 18, 2004 8:15 AM
To: wix...@li...
Subject: [WiX-users] InstallExecuteSequence table does not contain
InstallFiles and RemoveFiles entries

PROBLEM: "InstallExecuteSequence" table does not contain "InstallFiles" 
and "RemoveFiles" entries
if package includes only merge modules.

For example:

<?xml version="1.0" encoding="windows-1251"?>
<?define ProjectMsmPath  = "./msm"?>
<Wix xmlns="http://schemas.microsoft.com/wix/2003/01/wi">
  <Product Id="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
           Name="MyProduct"
           Version="1.0.0.0"
           Manufacturer="MyCompany"
           UpgradeCode="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
           Language="1049"
           Codepage="1251">

    <Package Id="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
             Keywords="shared, component"
             Description="desc"
             Manufacturer="Me"
             InstallerVersion="200"
             Languages="1049"
             Compressed="yes"
             SummaryCodepage="1251" />

    <Media Id="1" DiskPrompt="LABEL" Cabinet="myproduct.cab" 
EmbedCab='no' CompressionLevel='medium' />

    <Directory Id="TARGETDIR" Name="SourceDir">
          <Merge Id='MSM1' Language='1033' 
src='$(var.ProjectMsmPath)/MSM1.MSM' DiskId='1' />
          <Merge Id='MSM2' Language='1033' 
src='$(var.ProjectMsmPath)/MSM2.MSM' DiskId='1' />
    </Directory>

    <Feature Id="FEAT_MyProduct" Title="MyProduct" 
Description="MyProduct only feat." Level="1">
      <MergeRef Id='MSM1' />
      <MergeRef Id='MSM2' />
    </Feature>

      <CustomAction Id="DIRCA_TARGETDIR" Property="TARGETDIR" 
Value="[SystemFolder]" Execute="firstSequence" />

      <AdminExecuteSequence>
         <Custom Action="DIRCA_TARGETDIR" 
Before="CostInitialize">TARGETDIR=""</Custom>
      </AdminExecuteSequence>
     
      <InstallExecuteSequence>
         <RemoveExistingProducts 
After="FindRelatedProducts">PREVIOUSVERSIONSINSTALLED</RemoveExistingProduct
s>
         <Custom Action="DIRCA_TARGETDIR" 
After="ValidateProductID">TARGETDIR=""</Custom>
      </InstallExecuteSequence>

      <!-- other stuff here -->
        ...

   </Product>
</Wix>

Assuming the msm-files are authored properly and each one has to install 
at least one file.
The wxs-file will compile and link without warnings and errors, but 
resulting msi-file will not install any files to destination directory.
I can fix the problem just adding missing table entries manually, like this:
...
      <InstallExecuteSequence>
         <RemoveFiles />
         <InstallFiles />
         <RemoveExistingProducts 
After="FindRelatedProducts">PREVIOUSVERSIONSINSTALLED OR 
UPGRADE_1</RemoveExistingProducts>
         <Custom Action="DIRCA_TARGETDIR" 
After="ValidateProductID">TARGETDIR=""</Custom>
      </InstallExecuteSequence>
...

So,  is there a bug in WiX toolset behaviour (the entries has to be 
added automatically) or this is by design?
NOTE: using WiX 2.0.2328.0


Thanks



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
WiX-users mailing list
WiX...@li...
https://lists.sourceforge.net/lists/listinfo/wix-users