Hello: Has anyone considered using name-based (e.g. URL-based) UUID's, as specified in RFC 4122, to reduce the tedium of creating Windows Installer packages with WIX? This would be especially helpful for component GUID's. Maybe the Component element could have an optional GuidUrl attribute, which would create a version 3 (MD5 hash) or version 5 (SHA-1 hash) from the specified URL. To reduce repetition in the source file, the author could use WIX variables in this attribute, like this:
<Component Id="Foo" GuidUrl="$(var.ComponentBaseUrl)/foo" DiskId="$(var.DiskId)"> It would certainly beat running uuidgen for each component. Are there any problems with using RFC 4122 name-based UUID's as Windows Installer GUID's? I've never really understood the difference, if any, between a UUID and a GUID. It looks like this idea should work, but I'm new to Windows Installer and WIX, so I may be missing something. Thanks. -- Matt Campbell Lead Programmer Serotek Corporation www.freedombox.info "The Accessibility Anywhere People" ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
