I'm working with two layers of libraries - one is the Microsoft data
application framework, which requires a config file to obtain database
connection information. The second, a business objects layer, depends on the
first for communication with the database. I don't have the option to change
either for this particular project.

In order to better utilize our "layout" group, who have very little
technical ability beyond HTML and CSS, I am attempting to make our growing
controls library, mostly grids showing various lists and details, to load
default states at design time, using live data. This will allow me to sell
the idea of using Visual Studio's Forms designer to the layout group, since
I could say dragdrop will make designing trivial, and "what you see is what
you get". In theory they would no longer have to mock up stuff by hand.
Rather, a spec could be executed at the control level, and instead of me or
someone else in development making the forms, they do it, and the events in
the code behind can be wired up later.

So... what I am looking to do is to somehow give VS a path to use to look
for config files at design time, or otherwise tell it to also copy config
files when it is copying the dlls to the design time executable folders.

Paul