We use auto-generated Product GUIDs almost exclusively where I work. I really haven't found a downside to it, at least for our uses. As for detecting old products, it is still easy to detect them. Instead of looking them up using explicit ProductCodes you use the Upgrade table with the UpgradeCode and a version range. This seems to be a more reliable way of finding older products anyway, assuming you keep your UpgradeCode static but most everyone does that.
The only potential downside could be based on what your patching/upgrade strategy. So far we are only doing major upgrades for all our MSIs, so changing Product GUID every build doesn't have any impact. If you do want to patch or apply small updates, depending on the methods of applying those patches and small updates, whether the ProductCode has changed or not matters. The Windows Installer SDK does not recommend using patches for updates that change the ProductCode. That is the only potential issue I can think of when using auto-generated ProductCodes. There could be other issues but I haven't run into any. -Mike -- View this message in context: http://n2.nabble.com/Auto-generated-vs-statically-assigned-GUIDs-tp4670083p4670397.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
