Thanks Rob,

Yep, my MSI isn't changing. I don't seem to be able to determine why it
thinks the hash doesn't match.

If build 153 created the MSI, and builds 153, 154, 155 etc are looking at
the same DownLoadURL location (and presumably the same target hash values),
why do Bootstrappers 154 and 155 onwards generate different hash values to
compare against? What items need to be static in order to come up with the
same hash code?

NB I'm planning never to change the sharedcomponents.msi... I may later have
to create shared2.msi.. shared3.msi etc..



--
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-tp7584968p7585100.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