When a .NET package is successfully installed as a prerequisite for our Burn bootstrapper application, and the user cancels the install, the bootstrapper package is still listed in the Add/Remove programs. I understand that the .NET package is part of the bundle but from a user's perspective none of the product has technically been installed. Especially, when someone takes a look in the Add/Remove programs window, the bundle is there, and they assume everything is in place.
Are there any settings to prevent this from happening? Alternatively, what are the strategies to deal with this scenario? This e-mail contains IPFX information which may be privileged or confidential and is intended for use only by the individual(s) or entity named above. If you are not the intended recipient, note that disclosing, copying, distributing or using this information is prohibited. If you have received this e-mail in error, please advise immediately to the e-mail address above and permanently delete this message and any attachments. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. We monitor our e-mail system and may record your e-mails. Thank you. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users