First, thanks for reconsidering this and allowing the SiteId to be set but...
Quote: "Skipped doing all the hashing since it isn't deterministic for uninstall. Setting the SiteId should enable the scenario very well. Honestly, SiteId works pretty well in all 'controlled environment' cases." I don't think this statement is true for the following reasons: 1. In the environment I work in, which I don't believe is unusual, there is a farm for servers which many different development teams deploy to. Having to manually manage SiteId is not easy, (ok we could provide a tool to generate the hashed SiteId from the site name). Using the hashing method allows for 99% of sites to have unique Ids, for the few that clash this can be handled by simply renaming the site. 2. The current method of setting the SiteId to 1 more than the highest available isn't deterministic, why is the hash different? 3. Using the hashing method means it work in exactly the same way as IIS6 does. I know I'm pushing my luck but can I ask you to reconsider again. Thanks Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] ------------------------------------------------------------------------- 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
