StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1684607
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2009-11-06T00:24:01.747
FavoriteCount
0
LastActivityDate
2009-11-06T00:29:14.700
LastEditDate
2009-11-06T00:29:14.700
LastEditorUserId
592
OwnerUserId
592
ParentId
1682252
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
As iwo said, <a href="http://wix.sourceforge.net/manual-wix3/preprocessor.htm" rel="nofollow noreferrer">preprocessor variables</a> are your friend! However the example from iwo can (and will) violate component rules, as the component isn't 'stable'. Better to condition an entire component (or component group)... <pre><code><?if $(var.releasetype)=full ?> <ComponentRef Id="Somefile.dll" /> <?elseif $(var.releasetype)=enterprise ?> <ComponentGroupRef Id="SomethingElse" /> <?endif?> </code></pre> And then include the <code>Component</code> and <code>ComponentGroup</code>s in separate <code>Fragment</code> tags so that they will only be compiled when referenced :) <pre><code><Fragment> <Component Id="Somefile.dll" Guid="*"> <File Id="Somefile.dll" KeyPath="yes" Source="SourceDir\Somefile.dll" /> </Component> </Fragment> <Fragment> <ComponentGroup Id="SomethingElse"> <ComponentRef Id="Somefile.dll" /> <Component Id="AnotherFile.dll> <File Id="AnotherFile.dll" KeyPath="yes" Source="SourceDir\AnotherFile.dll" /> </Component> </ComponentGroup> </Fragment> </code></pre> Personally I use <a href="http://nant.sourceforge.net/" rel="nofollow noreferrer">nant</a> to call <code>candle</code> and <code>light</code> targets, defining different variables for various different builds and products, effective use of fragments and preprocessor variables provides a great opportunity for code re-use between projects, or various releases of the same project. In your case, to check if a file exists... then you'd just use the internal functions to define, or redefine a variable that is later passed to WiX. e.g.: <pre><code><if test="${not file::exists('something.dll')}"> <property name="releasetype" value="blahblahblah" /> </if> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWiX: Define a File component that may not exist
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USsaschabeaumont
UserOwnerUserId
1. USsaschabeaumont
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWiX: Define a File component that may not exist
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COSolved my problem. Thanks.
 singulars
 PostPostId
 PO
 UserUserId
 USnagul

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.