Config File?

With Isolated Stroage it saves it in the <user>/application data/ folder, which im pretty sure is rwx.

Registry is probably faster, but if I want to be able to add in the option to export and import a settings file, it would be easier with the XMl file, as I could just point to and overwrite the base file.

I think importing registry settings for the user would be more difficult.

Thanks anyways though.

Rather than the Registry you can always use a SpecialFolder. If you check MSDN you will see that they can be specific to a given user.

word on the street has it that the registry is on the out anyway. i can't remember where i read it, but somewhere in either msdn or some other microsoft literature, I read that they strongly encourage you not to use the registry.

if you just look at it from a deployment angle, you are far better having a config file that can be deployed with the app, or updated just by sending a new version of the config to the user.

I personally use the dataset.readxml for 90% of my configs. it's real simple to use.

I could do with a .config file for my DLL but I see it's not the same as that for an exe. I'm interested in a runtime variable which can be edited by admin, the variable might do something like point to alternative location for other assemblies..

Are the Settings in the Project Properties of any use?

I've already implemented with a Registry setting but it has been rejected, maybe due to possible installation issues or lack or safe editability, any one know what the recommendations are for settings/config file versus Registry entry?