StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11846595
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-08-07T12:59:50.943
FavoriteCount
0
LastActivityDate
2012-08-07T12:59:50.943
LastEditDate
2017-05-23T12:04:44.383
LastEditorUserId
-1
OwnerUserId
57883
ParentId
10316108
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Beware MSBuild and VSBuild DO differ. <a href="https://stackoverflow.com/a/1830650/57883">Afterpublish is VERY limited</a> <a href="https://stackoverflow.com/questions/8404114/how-make-msbuild-build-custom-target-specified-in-csproj-building-sln">Try having msbuild save the emitted sln</a> Also <a href="https://stackoverflow.com/questions/5556168/msbuild-script-utilizing-solution-information">here</a>. Have you verified the file is getting transformed at the expected time? Add in a <code><message importance="high" text="Doing Custom Transform" /></code> before your transformxml call, then another message with different text <code>Finished Custom Transform</code> after this call. <a href="https://stackoverflow.com/a/9059685/57883">This post</a> speaks directly to your desire to do things involving the specialized publishing targets. General msbuild debugging information: Hopefully this behavior IS msbuild dependant instead of VSBuild, since the two build processes differ. If you are in luck and this is following the same behavior as MSBuild would follow the msbuild debugging process: As with any magical behavior in msbuild, in your <code>CSProj</code> file look for any <code>import target=</code> code and go find those files. Following these through will lead you to the part that is making the decision about any of this. Also you can attach VS's debugger to your build process - <a href="http://blogs.msdn.com/b/visualstudio/archive/2010/07/06/debugging-msbuild-script-with-visual-studio.aspx" rel="nofollow noreferrer">http://blogs.msdn.com/b/visualstudio/archive/2010/07/06/debugging-msbuild-script-with-visual-studio.aspx</a> + <a href="http://blogs.msdn.com/b/visualstudio/archive/2010/07/09/debugging-msbuild-script-with-visual-studio-2.aspx" rel="nofollow noreferrer">http://blogs.msdn.com/b/visualstudio/archive/2010/07/09/debugging-msbuild-script-with-visual-studio-2.aspx</a> <a href="http://msdn.microsoft.com/en-us/library/ee216359.aspx" rel="nofollow noreferrer">Determining build order</a> Also in crank up the build verbosity temporarily <a href="http://blogs.msdn.com/b/msbuild/archive/2005/09/29/475157.aspx" rel="nofollow noreferrer">http://blogs.msdn.com/b/msbuild/archive/2005/09/29/475157.aspx</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTransformXml Web.config while publishing
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USMaslow
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.