StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15682656
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
5
CommunityOwnedDate
CreationDate
2013-03-28T13:07:10.477
FavoriteCount
0
LastActivityDate
2013-07-07T04:03:52.663
LastEditDate
2013-07-07T04:03:52.663
LastEditorUserId
63550
OwnerUserId
786103
ParentId
12823722
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
It had a number of steps. Remember I was running this from a bootstrapper, not an MSI file, whereby levarius's answer would have sufficed. Basically, I removed any of the launch logic that was posted in the original question, and created a new package, whose sole functionality was to kick off an application (using a custom action), and whose location had previously been saved in the registry - that is, the application running when it found that an update was available, set this item in the registry. The package (called PostInstall below) is then run ONLY if one of the other packages has been installed previously - found by the existence of a key in the registry (set in each product's MSI). This means that no application will be started automatically after a new install has completed. The following is from the bootstrapper bundle (WiX 3.6 in my case) <pre><code> <util:RegistrySearch Root="HKLM" Key="SOFTWARE\CompanyName" Value="ProductAInstalled" Variable="ProductAInstalled" Result="exists" Format="raw" /> <util:RegistrySearch Root="HKLM" Key="SOFTWARE\CompanyName" Value="ProductBInstalled" Variable="ProductBInstalled" Result="exists" Format="raw" /> <Chain>  <PackageGroupRef Id="NetFx40Web"/> <MsiPackage SourceFile="..\SetupProductA\bin\Release\SetupProductA.msi" InstallCondition="(chkProductA) OR (ProductAInstalled)" /> <MsiPackage SourceFile="..\SetupProductB\bin\Release\SetupProductB.msi" InstallCondition="(chkProductB) OR (ProductBInstalled)" />   <MsiPackage SourceFile="..\PostInstall\bin\Release\PostInstall.msi" InstallCondition="(ProductAInstalled) OR (ProductBInstalled)" /> </Chain> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POStart application after installation using WiX/Burn
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USPeter Mortensen
UserOwnerUserId
1. USFetchez la vache
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POStart application after installation using WiX/Burn
 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
 VTDownMod
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.