I really think that the feature of using the full redist package when available, and the web package as a fallback, should be in the engine. That way during layout, it can also just download the full package. Also the engine would take care of finding the package in the cache and automatically (well, actually the BA will probably have to permit it) fallback to the web download.
http://wixtoolset.org/issues/4183/ asks for the payload info to be separated from the package. The way I interpret that is to designate one of the child payloads as the PackagePayload and remove all of the payload attributes from the XxxPackage element. Then to implement the web package fallback, there would be another special payload, like WebPayload or AlternatePackagePayload. Does that make any sense? On Wed, Oct 22, 2014 at 6:34 PM, Bob Arnson <b...@joyofsetup.com> wrote: > On 22-Oct-14 19:15, Sean Hall wrote: > > So the install fails if the redist package doesn't pass verification, > > and the user has to delete it to make it work? Not very user friendly. > No different than any other failed package. > > > If you're modifying the InstallCondition, then you must be authoring > > your own package. > I'm authoring the canonical package. > > -- > sig://boB > http://joyofsetup.com/ > > > > ------------------------------------------------------------------------------ > _______________________________________________ > WiX-devs mailing list > WiX-devs@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-devs >
------------------------------------------------------------------------------
_______________________________________________ WiX-devs mailing list WiX-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-devs
