The documentation states the following for the Wix Guid attribute for the
Component element:
Guid
ComponentGuid<mk:@MSITStore:G:\src\working.server.spaces\public\ext\wix\3.0.4123.0\doc\WiX.chm::/html/wix_xsd_simple_type_componentguid.htm>
This value should be a guid that uniquely identifies this component's
contents, language, platform, and version. It's also possible to set the value
to an empty string to specify an unmanaged component. Unmanaged components are
a security vulnerability because the component cannot be removed or repaired by
Windows Installer (it is essentially an unpatchable, permanent component).
Therefore, a guid should always be specified for any component which contains
resources that may need to be patched in the future.
We happen to use MSIs without the update feature, because we install MSIs to a
server that we own and have complete control over. The server is never released
to end-users. Even a single file change in our deployment results in us
uninstalling the MSI and installing a new MSI.
In this scenario, can we safely set the GUID element's value to the empty
string?
The reason I ask is that we would like to use the cab caching mechanism. We run
into a problem though because WIX entries for directories are generated by a
tool. This tool cannot "remember" guids from previous runs, so always creates
new guids for each directory's components. However, by creating new guids, the
tool cannot leverage the cabinet cache.
Thomas
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
