Well, the peanut gallery is back. > Wow, no faith from the peanut gallery.
> If the file is signed (something else we calculate during build when > referencing the file) we will use the signature of the file not the hash. If > the signature on the file changed in between the point that you built and > the user downloaded the actual file, chances are the user has a file you > don't want them installing. <smile/> I understand your reasoning and even agree with it for the most part; however, I just checked my Bootstrapper directory and indeed there is not a file for the DotNet 3.5SP1 or Client installs (amongst others). I do see that the product.xml file has PublicKey listed for each PackageFile. That seems to be MUCH desirable to having to have a local copy of the file on the system that builds the BA. As you think about this issue, please consider that it would be beyond wonderful if WiX could use the same input (to define a file and its download) that the "GenerateBootstrapper" action uses so that we do not have to reinvent the wheel every time MS releases a new package. ---------------------------------------------------------------------- Roy Chastain ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
