StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6404342
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-06-19T18:32:17.987
FavoriteCount
0
LastActivityDate
2011-06-29T16:09:22.283
LastEditDate
2011-06-29T16:09:22.283
LastEditorUserId
30809
OwnerUserId
30809
ParentId
6399014
PostTypeId
2
Score
19
ViewCount
0
LastEditorDisplayName
text
Body
I figured this out shortly after posting it. Team Build supports the following values for RunCodeAnalysis: Always, Default, Never. In contrast, locally MSBuild supports True or False for RunCodeAnalysis. Why are they different? In looking at the Microsoft.TeamFoundation.Build.targets file, the following appears: <pre><code><Target Name="CoreCompileSolution"> <PropertyGroup> <CodeAnalysisOption Condition=" '$(RunCodeAnalysis)'=='Always'">RunCodeAnalysis=true</CodeAnalysisOption> <CodeAnalysisOption Condition=" '$(RunCodeAnalysis)'=='Never'">RunCodeAnalysis=false</CodeAnalysisOption> ... </PropertyGroup> ... </Target> </code></pre> These settings are then passed onto the msbuild process when it compiles the solution file. So in other words: Always tells MSBuild to compile all projects with RunCodeAnalysis=True Never tells MSBuild to suppress code analysis (RunCodeAnalysis=False) on all projects. ...and not specifying a value for RunCodeAnalysis means that MSBuild will respect the RunCodeAnalysis setting in the project file. Hence, the default setting. Simply removing the /p:RunCodeAnalysis from my original question had the correct result. Projects that have analysis turned on will run code analysis. Projects without the setting don't perform any extra work. More information about this is available here: <a href="http://www.bryancook.net/2011/06/build-server-code-analysis-settings.html">http://www.bryancook.net/2011/06/build-server-code-analysis-settings.html</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODisable Code Analysis for Some Projects using MSBuild
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USbryanbcook
UserOwnerUserId
1. USbryanbcook
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODisable Code Analysis for Some Projects using MSBuild
 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.