StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15383548
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-13T11:06:53.983
FavoriteCount
0
LastActivityDate
2013-03-13T11:06:53.983
LastEditDate
2017-05-23T11:52:59.190
LastEditorUserId
-1
OwnerUserId
806690
ParentId
5866954
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Regarding your first question: No, you don't need to. But why? I had difficulties to understand the windows installer rules in my side-by-side scenario. You really need to understand the concepts of <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/aa372795.aspx" rel="nofollow noreferrer">component rules (including when you need to brake them)</a> and <a href="https://stackoverflow.com/questions/2003043/what-is-the-wix-keypath-attribute">key paths</a>. WiX doesn't abstract these aspects away. <a href="https://stackoverflow.com/a/5869087/806690">This answer</a> does already highlight possible interferences. Let's consider a few examples. <ul> <li>The GUID of the component with the application executable does not need to be changed. This breaks the component rules, but it works, as both versions of the product define the same component in a non-interfering way.</li> <li>A resource shared by both versions is not directly supported. A prominent example is the use of file extensions using ProgIDs, as shown <a href="http://msdn.microsoft.com/en-us/library/vstudio/bb166183.aspx" rel="nofollow noreferrer" title="Managing Side-by-Side File Associations">here</a>. If you change the GUID (also happening when using the "*" GUID), the extension will be removed when uninstalling either version. If you don't change the GUID, the extension will be retained, but point to the version which was installed most recently. You may go with this option as the lesser of two devils, supporting at least a scenario where users uninstall the versions in the same order in which they installed them. There is a pitfall here: The extension needs to be the key path of the component. This makes the usage of the ProgID element problematic in a side-by-side scenario as you'll get the ICE69 warning in case you don't put the ProgID element in the same component as the referenced file. Further more, it's an implementation detail of WiX which registry entry it generates will be the key path.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWiX project allowing side-by-side installation
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. UStm1
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.