wrong default installation directory for non-admin installations

[donovaly]

If JabRef 3.3 is installed on Windows only for the current user (without admin privileges) the default installation folder proposed by JabRef is
C:\Users\JabRef
this is incorrect, according to the Windows guidelines it must be
C:\Users\AppData\Local\JabRef

All other programs I know respect this default installation folder for current users.

[stefan-kolb]

Are you sure this shouldn't go to APPDATA\Roaming so the user profile data gets synched when in a Domain? Could you provide links where this best practice is specified?

[stefan-kolb]

We can discuss this in this context:https://msdn.microsoft.com/en-us/windows/uwp/app-settings/store-and-retrieve-app-data
Would enable preference sharing on multiple PCs?

[donovaly]

Are you sure

Sure ;-)
The default installation folder for local users is available via teh %LOCALAPPDATA% variable.
It points you automatically to
%USERPROFILE%\AppData\Local
reference:
https://blogs.msdn.microsoft.com/patricka/2010/03/18/where-should-i-store-my-data-and-configuration-files-if-i-target-multiple-os-versions/

[stefan-kolb]

Why not use the Roaming folder to keep JabRef synchronized for users inside domains?

[donovaly]

Why not use the Roaming folder to keep JabRef synchronized for users inside domains?

Because Roaming is for installations for all users on a PC. A local installation (only for the current user) cannot be synced with others - that's the concept of the local installation.

[donovaly]

Can you please try a version from http://builds.jabref.org/win-install

Done. This does not solve the problem because it tries now to install in the same folder where the installer was started from. So when I execute the installer from C:\Test it proposes C:\Test\JabRef as install folder.
So this bug is not fixed. Please reopen this bug report.

[stefan-kolb]

Thanks for pointing this out 👍
I incidentally used the wrong method to retrieve the environment variable 😊
This should be fixed in current master. Please try the latest build from http://builds.jabref.org/master.

[donovaly]

Please try the latest build

Done. Many thanks! The bug is now correctly fixed. So from my point of view all install issues are solved. I am looking forward for JabRef 3.4 to use its installer.