Looks like using the generated guids for component ids will work out for you. The only two gotchas you need to look out for are:
If you change a keypath (either directory tree or targetfilename for a keypath) and you have other resources in that same component (registry/COM registration/other files), those other resources could be wiped out if you do late scheduling of the RemoveExistingProducts action (it is a violation of the component rules, after all). The rule of thumb is: if you change the filename, change all the COM/registration that goes with it in the component. If you do the same keypath change mentioned above using a non-major upgrade, you will also cause major pain. The FIPS switch is for those that are building on "high security" platforms (those where "insecure" algorithms such as MD5 have been disabled/removed) due to some US Department of Defense or other similar requirement. If you don't know about it, you aren't doing it <smile/>. http://en.wikipedia.org/wiki/FIPS_140 -----Original Message----- From: MikeR [mailto:michael.ru...@gmail.com] Sent: Monday, January 25, 2010 2:02 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX syntax for GUIDs for 32-bit/64-bit components What is the FIPS switch? I haven't heard of it, so I'm assuming it's not something I'll likely be changing in our builds. We do our builds through Team Build, so whatever default settings are passed to the WiX tools from WiX MSBuild tasks are what I'm using and won't likely be changing anytime soon. Our Directory structure is staticly constructed. Our component and key file names are either static or based on Visual Studio project references. I use $(var.<ProjectName>.TargetFileName) in my component id, file id and file name attributes. However, as you stated if the target directory or key file name are changing at all the component GUID should be changing as well. I already have the "magic" set up to alter the directory structure to use ProgramFilesFolder/ProgramFiles64Folder based on the built-in Platform WiX variable from Visual Studio/Votive with some preprocessor logic, so I think using the "*" for my component GUIDs will work well and make our WiX code look much nicer. Thanks for the detailed information. -- View this message in context: http://n2.nabble.com/WiX-syntax-for-GUIDs-for-32-bit-64-bit-components-tp444 0404p4457060.html Sent from the wix-users mailing list archive at Nabble.com. ---------------------------------------------------------------------------- -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
