StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3005776
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-06-09T12:36:21.257
FavoriteCount
0
LastActivityDate
2010-06-09T12:36:21.257
LastEditDate
LastEditorUserId
0
OwnerUserId
323979
ParentId
2991904
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
<p>You can try to use additional metadata for item SolutionToBuild. Some work with recursion and voilà!</p> <pre><code><?xml version="1.0" encoding="utf-8" standalone="yes"?> <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> <ItemGroup> <SolutionToBuild Include="$(SolutionRoot)\Scribble\levelone.sln"> <DependsOnSolutions>$(SolutionRoot)\Scribble\leveltwo.sln</DependsOnSolutions> </SolutionToBuild> <SolutionToBuild Include="$(SolutionRoot)\Scribble\leveltwo.sln"> <DependsOnSolutions>$(SolutionRoot)\Scribble\levelthree.sln;$(SolutionRoot)\TestProject1\TestProject1.sln</DependsOnSolutions> </SolutionToBuild> <SolutionToBuild Include="$(SolutionRoot)\Scribble\levelthree.sln" /> <SolutionToBuild Include="$(SolutionRoot)\TestProject1\TestProject1.sln" /> </ItemGroup> <Target Name="Build"> <MSBuild Projects="$(MSBuildProjectFile)" Targets="BuildSolution" Properties="SolutionFullPath=%(SolutionToBuild.Identity)"/> </Target> <Target Name="BuildSolution"> <CreateItem Condition="'%(SolutionToBuild.Identity)'=='$(SolutionFullPath)'" Include="%(SolutionToBuild.DependsOnSolutions)"> <Output TaskParameter="Include" ItemName="DependentSolutions" /> </CreateItem> <Message Text="Building solution $(SolutionFullPath)..." /> <Message Text="Solution $(SolutionFullPath) depends on %(DependentSolutions.Identity)..." Condition="'@(DependentSolutions)'!=''"/> <Message Text="Building dependent solutions..." Condition="'@(DependentSolutions)'!=''"/> <MSBuild Projects="$(MSBuildProjectFile)" Targets="BuildSolution" Properties="SolutionFullPath=%(DependentSolutions.Identity)" Condition="'@(DependentSolutions)'!=''"/>  <Message Text="Building solution $(SolutionFullPath)... OK" /> </Target> </Project> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMSBuild Build Sequence
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSergio Rykov
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POMSBuild Build Sequence
  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
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.