Replies: 3 comments 2 replies
-
On what operating system do you use |
Beta Was this translation helpful? Give feedback.
-
I second @igloo15's suggestion regarding the in app updater. Maybe one of the following projects could be used for the implementation of this updater?
|
Beta Was this translation helpful? Give feedback.
-
I'd also love to get an in-app updater. I just tried WinGet, but it downloads the application into its own winget directory within AppData>Local>Microsoft>Winget>Packages, ignored my previous download, which I dislike, and as the application .exe is a standalone and doesn't have an install process that adds the program to the StartMenu, I had to go digging to find the installed application. I'd much prefer to have the application extracted and placed in my C://Program Files folder like any other x64 windows app, and have the in-app updater keep the install location there (or wherever the last .exe was located). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Right now when an update is released it requires going to github downloading the file and extracting it. Then updating the binaries where ever you have it installed with the new ones. This is a cumbersome process but typically fairly easy and straight forward. It becomes more annoying though if there are multiple releases in a short period of time.
The user then can either turn off updates which is probably not recommended or update each version as they release. I propose 2 ideas that could be done independently or at the same time.
I think doing both options is a good idea but doing option 1 shouldn't be too difficult to implement while a more long term solution is developed like option 2.
Beta Was this translation helpful? Give feedback.
All reactions