StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow to configure multiple modules using .net configuration files
primarykey
Id
496469
data
AcceptedAnswerId
0
AnswerCount
5
ClosedDate
CommentCount
0
CommunityOwnedDate
2009-02-03T15:53:14.773
CreationDate
2009-01-30T17:46:21.210
FavoriteCount
0
LastActivityDate
2009-02-09T06:35:10.577
LastEditDate
2009-02-03T15:53:14.773
LastEditorUserId
32313
OwnerUserId
32313
ParentId
0
PostTypeId
1
Score
0
ViewCount
1078
LastEditorDisplayName
Jojoe
text
Body
I have a few .net modules/libraries I am referencing from my main application. Each of the modules/libraries can be configured and after I build them they each have a configuration file such as MyModule1.dll.config, MyModule2.dll.config. When I build my main application an app.config file is outputted to the output directory. I am wondering how to configure MyModule1, MyModule2 etc. Should I include config sections for each in the app.config file or should I have a separate config file for each module where I load a config file for each one? The separate config per module is described here: <a href="http://social.msdn.microsoft.com/Forums/en-US/netfxbcl/thread/2710647c-6414-42c4-90b7-fd7603f55ae0/" rel="nofollow noreferrer">http://social.msdn.microsoft.com/Forums/en-US/netfxbcl/thread/2710647c-6414-42c4-90b7-fd7603f55ae0/</a>? This would mean that I would copy MyModule1.dll.config and MyModule2.dll.config to the output directory as well. Can anyone give me some advice on what is the best practice/proper way to do this? Edit: From MyModule1.dll I can explicitly load MyModule1.dll.config using <pre><code>Uri p = new Uri(System.Reflection.Assembly.GetExecutingAssembly().CodeBase); Configuration config = ConfigurationManager.OpenExeConfiguration(p.LocalPath); </code></pre> but if MyModule1.dll references and uses one of my common libraries MyCommonLib.dll how can I have MyCommonLib.dll be configured from the same config file MyModule1.dll.config?
Tags
<.net><configuration>
Title
How to configure multiple modules using .net configuration files
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USFadeproof
UserOwnerUserId
1. USFadeproof
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POHow to configure multiple modules using .net configuration files
 UserUserId
 USFadeproof
 VoteTypeVoteTypeId
 VTBountyStart
2. VO
 singulars
 PostPostId
 POHow to configure multiple modules using .net configuration files
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTBountyClose
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.