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

Installing vNext of existing app, doesn't update existing app #355

Closed
augustoproiete opened this issue Nov 20, 2015 · 3 comments
Closed

Comments

@augustoproiete
Copy link

Is this the expected behavior?

image

@augustoproiete augustoproiete changed the title Installing vNext of existing app, installs both versions instead of updating existing app Installing vNext of existing app, doesn't update existing app Nov 20, 2015
@nblumhardt
Copy link
Member

Thanks for the note. To update an app the "Manage..." link will do this; I am not sure that supporting multiple versions the way we do now is great, but I'm also not sure disallowing it makes sense either. I'm inclined to close this as it stands - what do you think?

@andymac4182
Copy link

Maybe an Update button next to Manage... when there is an update available for that application will encourage people to update instead of installing multiple versions accidentally and when installing a new version of an existing app ask if they meant to update that application. This would allow the existing behaviour to still work while helping to guide users to the outcome they are looking for.

@nblumhardt nblumhardt added this to the 3.4-pre milestone Aug 29, 2016
@nblumhardt
Copy link
Member

In 3.4, there is now a "Check for package updates" setting and an "Update" button that will be displayed when app updates are available.

image

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

3 participants