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

Installer not removing/closing old version #1

Closed
traynier opened this issue Nov 22, 2014 · 5 comments
Closed

Installer not removing/closing old version #1

traynier opened this issue Nov 22, 2014 · 5 comments
Labels

Comments

@traynier
Copy link

First off, awesome work! I love it. :)

A few oddites in the "Check Update" and installing 1.0.0.2 over 1.0.0.1.

  1. Have 1.0.0.1 installed.
  2. Check updates, and download and run the 1.0.0.2 installer
  3. It complains about Vagrant manager already running, and offers to close it. However, it does not close cleanly and fails - the icon disappears from the taskbar but it is still running as a process until I kill it in Task Manager.
  4. I now have both 1.0.0.1 and 1.0.0.2 listed in Windows "Uninstall a program" - ideally it should remove 1.0.0.1 as part of the 1.0.0.2 install.
  5. It also seemed to lose my bookmarks
@amitailanciano
Copy link
Member

We'll look into this, thanks for letting us know

@cfoellmann
Copy link

Maybe using a different update library? https://autoupdaterdotnet.codeplex.com/
Or did you report the issue to https://github.com/sparkle-project/Sparkle ? If this is the right library.

@cfoellmann
Copy link

Sorry- Was not the right library.
You use https://github.com/sparkle-project/Sparkle , right? Seems very outdated. Maybe there is the problem.

@amitailanciano
Copy link
Member

Sparkle only checks for updates and notifies users when an update is available, it will also download the executable for you, all of which works well; the problem appears to be related to the actual installer. Right now we're using Inno Setup, but at this point we'll probably try using the built-in Visual Studio tools to package it and see if that resolves the issue.

@amitailanciano
Copy link
Member

This should be resolved in 1.0.0.4

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

No branches or pull requests

3 participants