Thanks for the reply. I agree, I am re-thinking the architecture behind all this. It looks like my boss would prefer me to actually define the platform as a Web Service anyway, due to the number of clients running it. The service will then be hosted on our servers, so if we need to patch it, we can do. Wheras if it were a DLL, then it would need to be patched on each and every server.
The current setup is: DLL output, with the config file next to it (so it pulls the settings from the dllname.dll.config
file in the same directory).
I then moved the DLL file, and accompanying config file to the bin
directory on the a website. When trying to execute a method within the DLL, it then fell over as it was unable to retrieve the connection string.
I have been doing some more digging, and there are several sites suggesting that if I place settings in the AppSettings section of the DLL's config, and the ConnectionStrings in the ConnectionStrings section of the DLL's config, I should then be able to copy these entries to the Web.config when the DLL is hosted on a web server. However, I can't seem to get this to work either...
Seems odd, I would have expected this sort of process to work, since its common across both Windows and Web based applications?