是否可以在解决方案中的多个项目之间共享 web.config？（ASP.NET）

Question

I have a solution composed of a web application and multiple projects, is it possible to share the configuration in the web application across all the solution?

Thanks

Answer 1

I looks like it is possible, you can try following:

You can copy your web.config file to the root folder of your solution. Then create solution folder (which does not belong to any of your projects) and add your file there (via Add Existing Item popup menu item). Delete web configs from your web sites. After that you can select Add Existing Item from popup menu on your both web projects, select your web.config file from the solution root and click Add As Link . After that you will have links to your web config files instead of real ones in your solution.

On the other hand I'm not sure if sharing of the web.config files among different projects is a good idea, because usually web.config has some specific condifuration for each separate application.

Answer 2

No, it is not possible. A web.config file need to be placed at the root folder of each web site. You could have a common web.config file copied to the root of each site as a build step of the project so that at runtime ASP.NET can find it.

Answer 3

Web.config files contain cascading overrides of a higher web.config file settings. So if you would place a web.config in the root of IIS or adjust settings in the machine.config or standard web.config of the .NET framework (C:\\Windows\\Microsoft.NET\\Framework\\v2.0.50727\\CONFIG for example).

The best example's probably the use of the LocalSqlServer connection string. It's defined in the machine.config as

<connectionStrings>
    <add name="LocalSqlServer" connectionString="data source=.\SQLEXPRESS;  
    Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;
    User Instance=true" providerName="System.Data.SqlClient"/>
</connectionStrings>

If you would use the Login control for example and would debug and request the connectionstrings then this one will be included as well.

So if you need some settings common to multiple applications place them in a web.config file which is high enough in the hierarchy, ultimately in the machine.config.

Answer 4

There's another alternative, and that is to put in a Pre-build command to copy the web.config from one folder to your destination folder. Let's say you had 3 projects. Project A has the "master" web.config.

In Project B and Project C, set up a pre-build to copy the web.config to the root of each project file, overwriting the web.config that exists in those folders.

The main problem with this is that you'll probably have specific bindings in each web.config that gets overwritten.

If your goal is to copy appSettings and possibly connectionStrings, you could do the same pre-build as above, but keep the appsettings and connectionstrings in a separate file from the web.config, then specifically open the settings file and read the content yourself using the WebConfigurationManager.OpenWebConfiguration method.