StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15891101
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-04-09T00:01:10.573
FavoriteCount
0
LastActivityDate
2013-04-09T00:01:10.573
LastEditDate
LastEditorUserId
0
OwnerUserId
191591
ParentId
15882300
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You can do it using its "loosely" typed model, basically for reading it for Default Web Site would look like: <pre><code>using (ServerManager serverManager = new ServerManager()) { Configuration webConfig = serverManager.GetWebConfiguration("Default Web Site"); ConfigurationSection section = webConfig.GetSection("system.webServer/defaultDocument"); foreach (ConfigurationElement item in section.GetCollection("files")) { Console.WriteLine(item["value"]); } } </code></pre> You can also generate strongly-typed wrappers for collections and entries you want to use frequently which makes it a lot cleaner and prevents mistakes, that would make it look like: <pre><code>using (ServerManager serverManager = new ServerManager()) { Configuration webConfig = serverManager.GetWebConfiguration("Default Web Site"); DefaultDocumentSection section = (DefaultDocumentSection)webConfig.GetSection("system.webServer/defaultDocument", typeof(DefaultDocumentSection)); foreach (FileElement item in section.Files) { Console.WriteLine(item.Value); } } </code></pre> And for that to work you need the following "strongly-typed-wrappers": <pre><code>public class DefaultDocumentSection : ConfigurationSection { private FilesCollection _files; public FilesCollection Files { get { if (_files == null) { _files = (FilesCollection)base.GetCollection("files", typeof(FilesCollection)); } return _files; } } } public class FilesCollection : ConfigurationElementCollectionBase<FileElement> { protected override FileElement CreateNewElement(string elementTagName) { return new FileElement(); } } public class FileElement : ConfigurationElement { public string Value { get { return (string)base["value"]; } } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC# Iterate 'Default Document' IIS 7 feature
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USCarlos Aguilar Mares
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POC# Iterate 'Default Document' IIS 7 feature
 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
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.