Thanks for information on FIPS, I'm pretty sure I won't be needing to work with that at all.
This product is a server/client configuration. The server is almost entirely .NET, we do have one service that requries a few registry keys but it's not for COM registration or anything just application settings and I'm keeping the keys in a separate component from the file. Nearly all components are one binary file and nothing else, there are a few components with multiple files for resource files, sql scripts used in our database configuration, etc and I'm continuing to use static GUIDs to manaage those few cases. On the client-side, I'm specifically keeping it one file per component, even for images and other resource files to allow for more flexibility in upgrading should we choose to do minor upgrading/patching down the road but currently our upgrade strategy for both client/server is major upgrades only with early-scheduled RemoveExistingProducts. I made all the changes yesterday and it all seems to be working quite well. I've verified the component GUIDs are being generated consistently and differ appropriately between the x86 and x64 builds. This WiX looks a lot better and will be more manageable going forward. Thanks for all your help! -- View this message in context: http://n2.nabble.com/WiX-syntax-for-GUIDs-for-32-bit-64-bit-components-tp4440404p4461258.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
