The ComponentGroup element's Directory attribute sets where to install the
components that are in that ComponentGroup. You can also set this on each
Component element via the Component's Directory element. Also, many of the
Windows directories are already defined for you by the WiX framework, so you
don't need to create nested structures for them: 

http://wixtoolset.org/documentation/manual/v3/bundle/bundle_built_in_variables.html

<Fragment>
<Directory Id="TARGETDIR" Name="SourceDir">
  <Directory Id="SystemFolder" />
  <Directory Id="ProgramFilesFolder">
    <Directory Id="TSSHORTCUTS" Name="$(var.PRODUCTNAME_MAJORMINORVERSION)"
/>
  </Directory> 
</Directory>
</Fragment>

<Fragment>
  <ComponentGroup Id="MyShortcutsGroup" Directory="TSSHORTCUTS"
Source="...">
    
  </ComponentGroup>
</Fragment>




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-Fragments-and-Directory-Structure-tp7593019p7593166.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to