Hi Raj, thanks for your response. I can put all the third party components in their own MSI (in fact I have now done just that) but since the MSI is currently within the Bootstrapper.exe its self it will always get downloaded with each update.
*How* do I set this "thirdpartycomponents.msi" up to be a pre-requisite which is not physically included in the bootstrapper, but called by and downloaded by the bootstrapper if needed - as can be the case with the .net framework, for instance? Many 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-tp7584968p7585015.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 WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
