You mix things up pretty badly. The installation does not have an accessibility modifier, they are always publicly available. However, in a Winforms application, you do have the Application Settings property in the Properties window for the control. Right upstairs. And a modifier property. The latter is the default Friend in a VB.NET, Private project in a C # application. This determines the availability of the control variable, not the settings.
Yes, My.Settings gives you access to the parameter that stores the value of the control property. But that is where the good news ends. You should always specify the parameter value in the settings designer for the user. So that the value can be saved and restored when your program starts the backup.
Settings with a user area are stored in a file that is difficult to find. A typical path for such a file is C: \ Users \ hpassant \ AppData \ Local \ WindowsFormsApplication1 \ WindowsFormsApplication1._Url_2acx4ldi2zmg42elj3eyqq0snhqco4qe \ 1.0.0.0
The first part is me, the current user of my laptop. The bizarre part of the path name is the hash, a value unique to the name and version of the application. And probably something like moon phase when I compiled the application. The calculation algorithm for this hash is not documented. Just that it will be unique to my application and cannot be broken by another application.
And that in rub, one application cannot find user area settings for another application. You will have to refuse to use the settings if it is important to you. And replace it with, say, an XmlDocument in a well-known place.
Hans passant
source share