[kemwelly]

Then Please feel free to explain us why that function is "shit".
Our company saves settings like that since ages, never had any problems with that .

EDIT: nice answer from StackOverflow

The registry is a no-go. You're not sure whether the user which uses your application, has sufficient rights to write to the registry.

You can use the app.config file to save application-level settings (that are the same for each user who uses your application).

I would store user-specific settings in an XML file, which would be saved in Isolated Storage or in the Application Folder

Next to that, as from .NET 2.0, it is possible to store values back to the app.config file.

If you move the file or modify it in anyway, the settings gets cleared.

[kemwelly]

What? No.
If you edit the settings file and make it invalid, then yes, the settings get cleared. But why would you want to edit it anyway?

I meant the exe, not the file. Sorry