Nagstamon Windows installer overwrites custom startup shortcut

[PGomersall]

Installation of Nagstamon at least versions 3.16 and 3.16.1 overwrites startup shortcut, you need to check if this is custom (added paths) as overwriting could then break path to non-standard settings folder.
Or provide another method for defining a custom setting folder for either all users or specific user.

[HenriWahl]

Ho @PGomersall - I do not fully understand. What is the relation from startup shortcut and non-standard settings folder? How was it before?

[PGomersall]

Henri, In your configuration notes you state that appending a path to Nagstamons executables path in a startup shortcut you can use custom location for settings rather than in a user’s profile. On several systems we configure Nagstamon to start by using the allusers startup shortcut file that contains the following C:\ProgramData\.Nagstamon using "C:\Program Files\Nagstamon\Nagstamon.exe" "C:\ProgramData\.nagstamon". Th startup shortcut file get overwritten when we update the application using your setup installer. Pete Gomersall From: Henri Wahl ***@***.***> Sent: Monday, October 21, 2024 8:26 AM To: HenriWahl/Nagstamon ***@***.***> Cc: Peter Lindsay Gomersall ***@***.***>; Mention ***@***.***> Subject: Re: [HenriWahl/Nagstamon] Nagstamon Windows installer overwrites custom startup shortcut (Issue #1069) Ho @PGomersall<https://github.com/PGomersall> - I do not fully understand. What is the relation from startup shortcut and non-standard settings folder? How was it before? — Reply to this email directly, view it on GitHub<#1069 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKLA4W2HFSGN4ZV2WQHRQDLZ4UMJZAVCNFSM6AAAAABQKJ65ACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRXGAYDONZQGI>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[HenriWahl]

@PGomersall well, it's true that a config directory can be given at starting Nagstamon, but also the installer will always do his job and overwrite all files with new versions. So I fear you need to use your mechanism to deploy the customized startup file again to setup your version of it or just use an startup link located at another location, which won't interfere with Nagstamon setup.