Why is the diskId associated with a "file"? This precludes using fragments to catalog components that might need to be used by more than one installer.
I apologize for the length of the post. Hopefully the content is straight forward and simple. The documentation describes components as items that each have a unique guid, so that the component can be installed by more than one application installer as required w/o orphaning those components when uninstalling one of the applications. The documentation also describes Fragments as being useful because they can be "included" or "referenced" in more than one installer and insure that the identical guid is associated with the same component. This all points to the idea that components can be uniquely identified in a fragment and then packaged into different installers at a higher level. The trouble is, if the diskId is specified at the file level, there is no way to re-use this catalog of components stored in the fragment w/ different media layouts. If I need 2 installers (CD based and DVD) specifying the DiskId at this low level won't work. Example 1: Assuming I have 3 files... All will fit on the DVD, but only one will fit on each CD. If I specify the DiskId at the file level, everything always goes onto Disk1 unless I edit the "reusable" fragment. Example 2: I have hundreds of thousands of image files covering the USA. I want to catalog these image files along with their GUID into fragment and then create one installer for each state. For a Washington State installer I will have files that are wholly contained inside of Washington state, files that are partially inside WA and partially inside ID, and files that are partially inside WA and partially inside OR. The files that are partially inside WA and partially inside ID or OR will also need to be included in the Idaho State and Oregon State installers respectively. If a user installs WA, OR, and ID states, and then proceeds to uninstall one of them I want to insure that the shared files aren't uninstalled. I'm doing this by insuring that all 3 installers use the same GUID. I'm doing this by creating a single .wxs fragment for each state listing the filename and it's GUID. Unfortunately, the file element specifies the DiskId and only the "primary" state being installed will fit on the DVD. The partial files need to go onto DVD 2 (DiskId 2). Is it possible to use fragments like this? If not, I'll probably create a database with the guids and a tool to generate the installers themselves. Thanks, Craig --- http://www.overlandnavigator.com Touchscreen Friendly GPS Mapping No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.15.31/1130 - Release Date: 11/14/2007 9:27 AM ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
