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

ConfuserEx results in unique AppData settings path #69

Open
jcwild opened this issue Oct 4, 2024 · 1 comment
Open

ConfuserEx results in unique AppData settings path #69

jcwild opened this issue Oct 4, 2024 · 1 comment

Comments

@jcwild
Copy link

jcwild commented Oct 4, 2024

Describe the bug
When I increment the version of my application and Confuse it, any settings saved by my application get written to a new directory.

To Reproduce
Steps to reproduce the behavior:
Create executable that saves to Settings (Properties.Settings.Default.MySetting = MyValue)
Build the executable. Confuse the executable. Run, and verify that the settings are written out to a unique folder, rather than the same one each time.

Expected behavior
I expect settings to be written out to a folder like so (and this happens when I run my unconfused executable):

C:\Users\Me\AppData\Local\MyApp\MyApp.exe_Url_i2ownvsfltxne3fy0osiwnmd2jhktcpp
\1.0.0.0
\1.0.0.1
\1.0.0.2

This allows the application to upgrade settings every time the version is incremented.

But once the executable is confused, it gets written out like so:

C:\Users\Me\AppData\Local\MyApp\MyApp.exe_Url_w25haaskuf4mvt1a2arml03f2xlepfjq
\1.0.0.0
C:\Users\Me\AppData\Local\MyApp\MyApp.exe_Url_giaohb3ca0q3zcbkwtiy0plru3bcea5u
\1.0.0.1
C:\Users\Me\AppData\Local\MyApp\MyApp.exe_Url_kmqav53rwulqdqezsyyjt2btb4vgbj32
\1.0.0.2

This means the application can no longer find the previous settings, and so all settings are initialised every time the application is upgraded.

Additional context
Similar to issue being described here: https://stackoverflow.com/questions/70731670/auto-generated-appdata-local-folder-being-incorrectly-created

@jcwild
Copy link
Author

jcwild commented Oct 6, 2024

This seems to be resolved if you use a private key.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant