-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Remove Old Cura Version when installing a new version #13446
Comments
Hey @fexofenadine, Welcome to the Ultimaker Cura Github 🚀 The behavior you are describing is actually intended behavior. But you are pointing out correctly that we fail to enable you to remove your old version of Cura when installing a new version. We used to have a feature like that in our installing wizard but this has been removed without providing a proper alternative. We've added a ticket to the backlog with the intent to improve this. Thanks for the report! 👍 |
IMHO, the preference to use side-by-side should be an option, and not the default. Or, at the very least patch-level and minor version upgrades should overwrite previous editions, but it is reasonable to default to side-by-side for major upgrades. I can understand when major feature updates occur that you might want different versions, but it is extremely annoying when 5.1.0 and 5.1.1 are different installations even though the updates are minimal, and for many users not even relevant. I'd also like to point out that the uninstall of older versions also don't clean up after themselves, and "open with" in explorer generally is worthless since it might point to a version that you uninstalled years ago. (since I'm a seasoned developer, I've manually cleaned this up on my machines several times, but it is not for the feint of heart). Also, with the introduction of Basically CURA does not follow best practice for software upgrades, and this is probably causing more severe problems than the ones it is intending to solve. |
Application version
All
Platform
Windows 11
Printer
N/A
Reproduction steps
Actual results
Upgrading this application on Windows is a nightmare because each installer installs a new package to a new unique directory, and has a new unique package name. It does not clean up previous versions and leaves orphaned files and packages everywhere
Expected results
Installer should not include version numbers to allow in-place upgrades without creating duplicate installs and orphaned items
Project file
N/A
Log file
N/A
Additional information
Could affect installers on other platforms too, I dont have experience with those
The text was updated successfully, but these errors were encountered: