StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5347604
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-03-18T03:02:47.823
FavoriteCount
0
LastActivityDate
2011-03-18T03:02:47.823
LastEditDate
2017-05-23T11:51:14.380
LastEditorUserId
-1
OwnerUserId
125439
ParentId
5346336
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I don't know if there is a more automatic way to get each AppDomain to use the same config information, but you might be able to use the technique in this post: <a href="https://stackoverflow.com/questions/4091606/most-useful-nlog-configurations/4260142#4260142">Most useful NLog configurations</a> To set the configuration programmatically via XML. For each AppDomain you load, you could read the NLog config file and then set the XML on NLog in the new AppDomain. One possible solution for getting your global values to the new AppDomain would be to store them using CallContext.LogicalSetData. The values will flow to the new AppDomain. Write a custom LayoutRenderer to get the values using CallContext.LogicalGetData. The LayoutRenderer is pretty easy to write. See this post for an example of how to write a custom LayoutRenderer that looks up a value based on a key (just like the GDC). For the internals, just use CallContext.LogicalGetData to retrieve the value: <a href="https://stackoverflow.com/questions/3961815/custom-log4net-property-patternlayoutconverter-with-index">Custom log4net property PatternLayoutConverter (with index)</a> See this blog post by Jeffrey Richter about using the CallContext: <a href="http://www.wintellect.com/CS/blogs/jeffreyr/archive/2010/09/27/logical-call-context-flowing-data-across-threads-appdomains-and-processes.aspx" rel="nofollow noreferrer">http://www.wintellect.com/CS/blogs/jeffreyr/archive/2010/09/27/logical-call-context-flowing-data-across-threads-appdomains-and-processes.aspx</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONLog configuration across AppDomains
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USwageoghe
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PONLog configuration across AppDomains
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThanks! I hadn't heard of CallContext before
 singulars
 PostPostId
 PO
 UserUserId
 USBrandonAGr

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.