All, firstly I am aware of this very useful question and related answers C# DLL config file. However, I need some advice on the best way to proceed in my specific case.
I have a large application that uses embedded SQL. To make the burden of writing SQL easier I have developed an SQL Editor facility with a built in snippet library and other such niceties, alleviating users of the burden of launching Management Studio each time they want to test a query and providing a library of common commands. This utility is a good tool I may want to embed in other apps so I have made it a DLL. Now what are my options for storing the setting for this application?
Creating the settings using a .config file in the main application and pass a properties object to the DLL; which is saved by the main app on DLL closure. In this case (probably my best option) is there a pattern I can use to handle changes to my editors settings?.
Create a .config for the DLL and store the settings in the same place regardless of the calling app. [note, I have seen the problems with doing this in the linked question - I am only likely to ever have the DLL called from a single app].
Any other magical ways?
Thanks for your time.