StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
535932
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-02-11T08:39:24.327
FavoriteCount
0
LastActivityDate
2009-12-14T21:14:19.983
LastEditDate
2009-12-14T21:14:19.983
LastEditorUserId
63550
OwnerUserId
36465
ParentId
535255
PostTypeId
2
Score
13
ViewCount
0
LastEditorDisplayName
text
Body
SharePoint is not quite like what you're used to. My two main gripes are: Deployment: If your requirements are for a single production site (no staging/test/development sites) your best bet is probably to go with the <a href="http://en.wikipedia.org/wiki/Microsoft_Office_SharePoint_Designer" rel="noreferrer">SharePoint Designer</a> and hack stuff together directly on the production site (yes I know it's dirty). If you need those other environments you should produce deployment packages for everything (no xcopy deployment). Deployment packages are a <a href="http://en.wiktionary.org/wiki/PITA" rel="noreferrer">PITA</a> IMHO and are very easy to get wrong. IIS SharePoint basically takes over your <a href="http://en.wikipedia.org/wiki/Internet_Information_Services" rel="noreferrer">IIS</a> installation and introduces a new set of rules for where things are located etc. One gotcha is "ghosted" files. i.e. whenever a file is changed using the SharePoint Designer the file is backed up to a database and from now on IIS will only use the file in the database, so there is no use changing the one in the file system. To sum up: In my humble opinion if you are making a site where uptime isn't that important and you can afford to make mistakes in production, SharePoint can be good enough with the designer. If you are making a <a href="http://en.wikipedia.org/wiki/Content_management_system" rel="noreferrer">CMS</a> site where you need the code to go through multiple environments before it reaches production, (with <a href="http://en.wikipedia.org/wiki/Continuous_integration" rel="noreferrer">continuous integration</a>), I can think of no other .NET based CMS that does a worse job. You will spend a LOT of time grokking how to get the deployment routines to work for you, and you will spend a LOT of time with issues relating to "ghosted" files Good luck.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSharePoint for a C# ASP.NET Developer
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USPeter Mortensen
UserOwnerUserId
1. USAndreasKnudsen
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POSharePoint for a C# ASP.NET Developer
 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.