Using app.config when referencing different projects?

Question

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!

score 3 · Accepted Answer · answered Mar 21 '13 at 14:52

3

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 ;)

answered Mar 21 '13 at 14:52

Custodio

8,594
15
80
115

I try to anonymize anything I post on this site :) – sooprise Mar 21 '13 at 14:54
1

sure, you are right. I was just kidding. Success loading the configurations? – Custodio Mar 21 '13 at 14:55
Yeah I was able to get the code working, but now someone posted a different type of solution. – sooprise Mar 21 '13 at 15:01

score 1 · Answer 2 · answered Mar 21 '13 at 14:49

1

A .NET application has one configuration file. It usually has the name of the executable. .NET doesn't support a config file per assembly.

You should be passing the connection string from the executable to the logger project.

answered Mar 21 '13 at 14:49

Daniel Hilgarth

171,043
40
335
443

score 0 · Answer 3 · edited May 23 '17 at 12:14

0

The best option for you would be to load Project1 confing inside Project2 at run time. What I would do is to place configuration string (or custom configuration section if required) inside Project2 confing. This settings would basicly just tell app where to look Project1 config.

Once you have confing path you can load it like this:

    System.Configuration.ExeConfigurationFileMap configFile = new System.Configuration.ExeConfigurationFileMap();
    configFile.ExeConfigFilename = "my_file.config";
    config = System.Configuration.ConfigurationManager.OpenMappedExeConfiguration(configFile, System.Configuration.ConfigurationUserLevel.None);
    settings = config.AppSettings.Settings;

In this case I am accessing AppSettings from Project1.

And about custom configuration that I have mentioned, please see one of my posts, this one Custom configuration section will do the job if you will require more complex settings.

edited May 23 '17 at 12:14

Community

1
1

answered Mar 21 '13 at 14:57

Gregor Primar

6,759
2
33
46

So this would result in two different config files? I'm starting to think putting it all in one config file will just make things easier for people that are using them... – sooprise Mar 21 '13 at 15:02
Yes this solution is suitable for multiple config files if you don't want to duplicate settings between them. – Gregor Primar Mar 21 '13 at 15:05
I found simple in my projects, to have a different config file just for test projects. The rest is centralized in app.config of start-up project. If you have so many configurations may migrating this to database is a option, but then is another history. – Custodio Mar 21 '13 at 15:09

score 0 · Answer 4 · edited May 23 '17 at 11:58

0

If you use default Properties.Settings (difference between app.config and settings explained here) and you have Project1 referenced in Project2, then you may do it like this:

// in Project2: 
    string connectionstring = NamespaceOfProject1.Properties.Settings.Default.Project1ConnString;

edited May 23 '17 at 11:58

Community

1
1

answered Mar 21 '13 at 15:17

Arie

5,251
2
33
54

Using app.config when referencing different projects?

4 Answers4