Kelly is exactly correct. In this case, the first autogenerated GUID that is getting you is the Package/@Id. The MSI SDK says that the Package/@Id should be unique for every MSI file. Arguably you could say the Ids should be the same in this case (and you could override the autogenerate) but typically, people just save the "gold bits".
Kelly Leahy wrote: > > I don't know if it's possible to produce exactly the same MSI, but I > think your problem is related to automatically generated package codes > or product codes. If you want to be able to rebuild an MSI that acts > exactly the same as one that already went out the door (I think this > is generally a bad idea and that you should save every MSI that you > release somewhere 'special' rather than relying on being able to > rebuild them), you need to force all the "autogenerated" IDs to be > identical from one build to the next. The only way to do this is to > fully specify all those IDs (packagecode productcode upgradecode, > etc.) and then make sure you update them when appropriate (when > building a "new" version of the MSI). > > Kelly > ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
