OK.
I should have known - rob was right all along (smile)

*Assuming* that WiX generates it's hash values the same way as the ms "File
Checksum Integrity Verifier"
(http://download.microsoft.com/download/c/f/4/cf454ae0-a4bb-4123-8333-a1b6737712f7/windows-kb841290-x86-enu.exe)
then the hash values of the sharedcomponents.msi files are indeed different
between builds, although the files within them are exactly the same, and are
unchanged (these are the 3rd party components, not something we're
compiling), and in fact there were no code changes at all inbetween the
different builds, as I kicked off a 2nd build specifically to test the
scenario.

Presumably I need to set something in the Product.wxs file of the shared msi
so that unless the contents change (and they won't) the hash code will
remain static. 

Any guidance would be appreciated. Thanks





--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-create-and-reference-a-custom-pre-requisite-package-tp7584968p7585103.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to