Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Burn adds entry in Program & Features upon installing pre-requisite, even if user cancels the installation of non-permanent Product #4905

Closed
wixbot opened this issue Sep 23, 2015 · 3 comments

Comments

@wixbot
Copy link

wixbot commented Sep 23, 2015

Burn installs .Net framework as pre-requisite and launches the installation (Managed UI) of product with its first installation screen. At this point if user cancels the installation, there would be an entry of product left in Programs & Features applet of Control Panel as if product is installed. This actually creates a confusion to common users that if they have canceled the installation, how it seems to be installed there.

Now, if user tries to un-install, repair etc, it would re-launch the first installation screen of managed UI again, forcing users to first install the product.

If original source of installation is removed, this would end up with error, installed otherwise.

Burn should not add itself to Programs & Features if main product is not installed or canceled. Some flag should be available in Wix for Burn to allow this.

Originally opened by farrukh

@wixbot
Copy link
Author

wixbot commented Sep 23, 2015

http://wixtoolset.org/issues/4822/

Originally posted by barnson
Resolution set to duplicate
Status changed from Untriaged to Resolved

@wixbot
Copy link
Author

wixbot commented Sep 23, 2015

Well, following the mentioned thread http://wixtoolset.org/issues/4822/, I'm still unable to find any solution, although, it is taken as a Feature in 4822. So technically, it should not be marked as resolved..

Originally posted by farrukh
Status changed from Resolved to Untriaged

@wixbot
Copy link
Author

wixbot commented Sep 23, 2015

It's resolved as a duplicate because there's an existing feature request.

Originally posted by barnson
Status changed from Untriaged to Resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants