You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To me it seems that the usage of automatically generated guids for components is impossible for merge modules when using standard directories like "TARGETDIR".
The following error occurs when using automatically generated guids for components within a sub-directory of "TARGETDIR":
error LGHT0231: The component 'TestComponent' has a key file with path 'TARGETDIR\pacelab_eo-project.ico'. 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.)
Please let me know how to use automatically generated guids for components within this context.
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 7 days (the time period specified by
the administrator of this Tracker).
Generating component GUIDs relies on having a known location; TARGETDIR-based components are almost always retargeted, especially from merge modules, so the generation logic doesn't have the data it needs to generate reliable component GUIDs. Using directories like CommonFilesFolder works as expected. It also works if you use .wixlibs instead of merge modules, because Light.exe has a view into the entire package and can generate GUIDs when they're eligible.
To me it seems that the usage of automatically generated guids for components is impossible for merge modules when using standard directories like "TARGETDIR".
The following error occurs when using automatically generated guids for components within a sub-directory of "TARGETDIR":
error LGHT0231: The component 'TestComponent' has a key file with path 'TARGETDIR\pacelab_eo-project.ico'. 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.)
Please let me know how to use automatically generated guids for components within this context.
The text was updated successfully, but these errors were encountered: