In our MBA we implemented a setup wizard with a feature selection on the first step. My intention was to give a hint to the user in case of missing or invalid packages *before* he entered the necessary information and the installation actually begins.
Rob Mensching-7 wrote > > 1. If a package cannot be found, you will get a source resolution > callback. > > 2. At the very least Burn does a SHA1 hash of the files to verify they are > correct before installing them for security reasons. If you digitally sign > your payloads, Burn will verify the signatures instead of hashing (which > ends up being the same thing basically). > Unfortunately this does not happen until the installation started. It would be great if I could actively trigger those checks, e.g. via the IBootstrapperEngine interface. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-check-for-MSI-existence-and-validity-tp7158657p7172328.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
