Mremoteng: Portable Edition doesn't use user.config in AppData/Roaming

[AlacrityF42]

The Portable edition of mRemoteNG 1.75 RC1 saves user.config to both AppData\Local and AppData\Roaming. When you launch the software it doesn't look for AppData\Roaming, so it thinks you've never run the software before. This does not happen in version 1.72.

|Operating system | Windows 7 x64 |
|mRemoteNG version| 1.75 RC1 |

[sparerd]

Thanks for the report @AlacrityF42 , we will look into this.

[digitalexpl0it]

I am seeing the same issue, glade its not just me. I use roaming profiles and settings reset after each log off. Would be great if this could be fixed soon. Product has been a great tool and I appreciate the efforts on it.

[kmscode]

Comment from #488

mRemoteNG is installed on multi user environement (Terminal Server with Citrix Xenapp 6.5 in this case).
User profile is configured to roam. In this configuration, appdata/local content will be deleted at logoff.
Opening mRemoteNG, user.config stored (manually) in appdata/roamin will load correctly and all config are OK.
If you edit configuration using Tools/Options a new user.config is created in appdata/local (using running configuration parameters) and not in appdata/roaming.
Existing user.config stored originally in appdata/roamin will not be updated.
At Operating System user logoff the file is deleted because all appdata/local and subfolders are discarded in TS environement with roaming profiles.

[kmscode]

Tentatively scheduled for 1.76

[crfiemme]

488 refers to installed application not portable version ;-)

Thanks for linking #488 with this thread and sorry for duplicating.
Mirco

[kmscode]

@crfiemme

While I haven't fully found the issue yet, most of these types of problems have code like this:

#if !PORTABLE
        public static readonly string SettingsPath = Do the non-portable thing;
#else
        public static readonly string SettingsPath = Do the portable thing;
#endif

So the fix will likely be "the same" - or at least right next to each other. And best to handle this with the one bug to ensure that they are both fixed at the same time.

[kmscode]

Reviewing this further, this might ultimately be resolved with #487

[sparerd]

@digitalexpl0it In #704 the portable version was changed to save program settings in the same directory as mremoteng.exe. Would you consider that a valid fix for the issues you are seeing? Or would you like us to keep this open to add the option to save settings to AppData\Roaming?

[AlacrityF42]

That works. Thanks!

-- Chuck

On 12/1/2017 7:03 AM, David Sparer wrote:
>

@digitalexpl0it https://github.com/digitalexpl0it In #704
https://github.com/mRemoteNG/mRemoteNG/pull/704 the portable version
was changed to save program settings in the same directory as
mremoteng.exe. Would you consider that a valid fix for the issues you
are seeing? Or would you like us to keep this open to add the option
to save settings to AppData\Roaming?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mRemoteNG/mRemoteNG/issues/414#issuecomment-348517232,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYyFFMro2UynG7aNx1Olpeova8pZM8e4ks5s8BU4gaJpZM4MKPdR.

[sparerd]

Great! This will be available in v1.76