StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
486663
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2009-01-28T06:31:51.843
FavoriteCount
0
LastActivityDate
2013-05-27T19:40:18.417
LastEditDate
2013-05-27T19:40:18.417
LastEditorUserId
884784
OwnerUserId
13302
ParentId
460935
PostTypeId
2
Score
140
ViewCount
0
LastEditorDisplayName
text
Body
The basic <code><appSettings></code> is easier to deal with - just slap in a <code><add key="...." value="..." /></code> entry and you're done. The downside is: there's no type-checking, e.g. you cannot safely assume your number that you wanted to configure there really is a number - someone could put a string into that setting..... you just access it as <code>ConfigurationManager["(key)"]</code> and then it's up to you to know what you're dealing with. Also, over time, the <code><appSettings></code> can get rather convoluted and messy, if lots of parts of your app start putting stuff in there (remember the old windows.ini file? :-)). If you can, I would prefer and recommend using your own configuration sections - with .NET 2.0, it's really become quite easy, That way, you can: <ul> <li>a) Define your configuration settings in code and have them type-safe and checked </li> <li>b) You can cleanly separate YOUR settings from everyone else's. And you can reuse your config code, too!</li> </ul> There's a series of really good articles on you to demystify the .NET 2.0 configuration system on CodeProject: <ol> <li><a href="http://www.codeproject.com/KB/dotnet/mysteriesofconfiguration.aspx" rel="noreferrer">Unraveling the mysteries of .NET 2.0 configuration</a> </li> <li><a href="http://www.codeproject.com/KB/dotnet/mysteriesofconfiguration2.aspx" rel="noreferrer">Decoding the mysteries of .NET 2.0 configuration</a></li> <li><a href="http://www.codeproject.com/KB/dotnet/mysteriesofconfiguration3.aspx" rel="noreferrer">Cracking the mysteries of .NET 2.0 configuration</a></li> </ol> Highly recommended! Jon Rista did a great job explaining the configuration system in .NET 2.0.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPros and cons of AppSettings vs applicationSettings (.NET app.config / Web.config)
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USLuis
UserOwnerUserId
1. USmarc_s
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPros and cons of AppSettings vs applicationSettings (.NET app.config / Web.config)
 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. 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.