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

[Bug] Update ignore Portable status #80

Closed
1 task done
saminationdj opened this issue Nov 8, 2024 · 2 comments
Closed
1 task done

[Bug] Update ignore Portable status #80

saminationdj opened this issue Nov 8, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@saminationdj
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

When using the in-app updater, it ignores where the current EXE is located and installs in %localappdata% location instead.

Reproduction Steps

...

Expected behavior

Install in the same location as the portable version has been extracted.

Screenshots

No response

Device Info

Operating system: Windows

Additional context

No response

@saminationdj saminationdj added the bug Something isn't working label Nov 8, 2024
@saminationdj
Copy link
Author

This isn't a dig at you, but I hate that programs install in the appdata location. That's not its intended location on Windows.

@ungive
Copy link
Owner

ungive commented Nov 8, 2024

I will definitely improve this once I work on a proper "portable" version. The ZIP as it is right now is identical to what is installed via the exe installer.

Updates are installed to the local appdata folder for simplicity: No elevated privileges are required during first installation and while installing updates automatically. It's also a central place to manage installed versions which just makes things easier, so it was the obvious choice to go about this.

But I definitely hear you and I will give the option to go fully portable without any leftovers in system directories in a future update (not too far in the future).

Since there is already an issue for this (#47) I will close this issue.

@ungive ungive closed this as completed Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants