Dirk Ziegelmeier wrote
> here is a minimal mergemodule showing the error:
> 
> <?xml version="1.0" encoding="UTF-8" ?>
> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";>
>     
> <Module Id="MergeModule" Language="1033" Version="1.0.0.0">
>         
> <Package Id="{SomeGUID}" Manufacturer="ACME" InstallerVersion="200" />
>         
> <Directory Id="TARGETDIR" Name="SourceDir">
>             
> <Directory Id="CommonFilesFolder" />
>         
> </Directory>
>         
> <DirectoryRef Id="CommonFilesFolder">
>             
> <Directory Id="ComStaHelper" Name="ACME">
>                 
> <Directory Id="ComStaHelperComSta" Name="ComStaHelper">
>                     
> <Component Id="cComSTAHelper" SharedDllRefCount="yes">
>                         
> <File Id="ComSTAHelper" Name="ComSTAHelper.dll" Source="ComSTAHelper.dll"
> KeyPath="yes" Checksum="yes" />
>                     
> </Component>
>                 
> </Directory>
>             
> </Directory>
>         
> </DirectoryRef>
>     
> </Module>
> </Wix>
> W:\tmp\CommonFiles.wxs(14) : error LGHT0231 : The component
> 'cComSTAHelper.63744358_CA08_4563_B039_4BE7181B668E' has a key file with
> path 'TARGETDIR\acme\comstahelper\comstahelper.dll'.  Since this path is
> not rooted in one of the standard directories (like ProgramFilesFolder),
> this component does not fit the criteria for having an automatically
> generated guid.  (This error may also occur if a path contains a likely
> standard directory such as nesting a directory
> with name "Common Files" under ProgramFilesFolder.)

Apologies for the necropost, but this ( Bug #3121
<https://sourceforge.net/p/wix/bugs/3121>  ) looks similar to  Bug #2938
<https://sourceforge.net/p/wix/bugs/2938>   that I filed in May, where I
demonstrated that this differed from the behavior in WiX 3.5.  Rob, your
response at the time was that "Auto-generated Component GUIDs were never
supported in Merge Modules unless you used
Directory@ComponentGuidGenerationSeed."

My understanding is that is that "CommonFilesFolder" must be modularized
because of the way that MSI handles merges (Directory table can't reconcile
identical primary keys from multiple sources), and after it is modularized,
it is no longer a well-known root directory.  My best guess it that WiX 3.6
changed the Component GUID auto-generation to occur after property/directory
modularization rather than before.  

Rob, could you confirm whether this is considered a regression or working as
designed?

Thanks,
Mike



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-3-6-MergeModule-creation-regression-tp7581302p7581787.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to