But isn't it a mistake? I Because the settings must be stored in root
folder as a single file(whatever its extension is not matter, ini or
XML) and whereever aplication is moved to another location, then the
settings file is moved to new location together, too.
Think about .ini files (i don't know how they're used in VB.NET) but
since their existence, usually they are used to store application
settings placed in root folder of application. So, whereever
application is moved to, the settings file will be called even in new
location well although location change unline vb.net's my.settings
feature.
That was all i wanted to point out.
Thanks.
For this problem (setting loss due to application location change),
should i go with storing application settings with INI files instead
of XML files? I remember "ini" files can be stored on app's root
folder generally and is moved anywere with the application if a
location change occurs with no data loss.
By default .NET's "my.settings" feature saves .config (XML coded) file
to C:\Documents and Settings\<name>\Local Settings\Application Data
\<company> or similiar like that as user.config file and if i move my
app(not user.config) another location settings are lost.
So, should i change setting storage to ".ini" files which is very
classic?
How can i read / write to "ini" files? I read some resources claim
that an API call maybe needed, however some non-API methods were
succeced in some cases.
I hope to know more about ".ini" files for settings storage.
Thanks.