Q:

Using app.config when referencing different projects?

I'm using app.config files for the first time and am unsure how to proceed in a situation with project references and app.config files. Here's a description of my projects I'm working with:
Project1 (process logger) populates log table in database specified in Project1 app.config file.
Project2 (calculator) runs a calculation and populates a table in database specified in Project2 app.config file.  Records log using reference to Project1. 
When I reference Project1 in Project2, in my "Release" folder I do not see an app.config file for Project1.  What is the best way to handle this situation?  Instead of making the database configurable in an app.config file in Project1, should I instead make it a parameter for Project2 to specify (Project2.LogConnectionString is sent as a parameter to functions in Project1)?  Or is there a way to make the app.config file appear in my "Release" folder?
Any help would be appreciated, I have no idea what is the right way to do this.  Thanks!

A:

Configuration files are based on the startup project.
Which means that when you instantiate something from proj1 in proj2 (proj1 will be a reference in proj2) you can use the app.config from proj2.
Basically, you can store all config in proj2 and use as need.
btw, change the proj names ;)

