yes, thanks a bunch Jason. Those little gem's helped me fiture out the answer to my quetion.
On Tue, Jun 10, 2008 at 10:31 AM, Jason <[EMAIL PROTECTED]> wrote: > I would highly suggest reading Rob's series of blog posts "Deciphering > the MSI Directory table".. > Part 1 - http://blogs.msdn.com/robmen/archive/2005/06/21/431294.aspx > Part 2 - http://blogs.msdn.com/robmen/archive/2005/06/28/433241.aspx > Part 3 - http://blogs.msdn.com/robmen/archive/2005/07/04/435572.aspx > Part 4 - http://blogs.msdn.com/robmen/archive/2005/07/12/437912.aspx > Part 5 - http://blogs.msdn.com/robmen/archive/2005/11/04/489346.aspx > Part 6 - > http://blogs.msdn.com/robmen/archive/2006/10/12/deciphering-the-msi-directory-table-part-6-standard-directories.aspx > Part 7 - > http://blogs.msdn.com/robmen/archive/2006/10/17/deciphering-the-msi-directory-table-part-7-directories-are-properties.aspx > > On Mon, Jun 9, 2008 at 11:12 PM, Chris Mumford <[EMAIL PROTECTED]> > wrote: > > Hey Neil: > > > > Thanks for responding. Sure, I do have other directories like: > > > > <Directory Id="ProgramFilesFolder"> > > <Directory Id="DesktopFolder"> > > <Directory Id="SystemFolder"> > > <Directory Id="CommonAppDataFolder" Name="MyDataDir"> > > <Directory Id="ProgramMenuFolder"> > > > > But only 2 of these are direct children of the parent TARGETDIR folder so > > things seem a bit arbitrary here. Why not just call the top level > > <Directory> tag <Directories> since there really isn't the parent child > > relationship that the file format suggests - at least suggests to me. The > > larger mystery is the relatioship between the ID and the Name. I'm sure > I'll > > figure it out eventually... > > > > -Chris > > On Sun, Jun 8, 2008 at 9:03 PM, Neil Enns <[EMAIL PROTECTED]> > wrote: > > > >> What do you have underneath your <Directory> element? Generally you put > >> another <Directory> element in to make the files go where you want, as > in > >> this example from "Authoring your first .wxs file" in the wix help: > >> > >> <Directory Id='TARGETDIR' Name='SourceDir'> > >> <Directory Id='ProgramFilesFolder' Name='PFiles'> > >> <Directory Id='MyDir' Name='Test Program'> > >> <Component Id='MyComponent' > >> Guid='12345678-1234-1234-1234-123456789012'> > >> <File Id='readme' Name='readme.txt' DiskId='1' > >> Source='readme.txt' /> > >> </Component> > >> </Directory> > >> </Directory> > >> </Directory> > >> I'm sure there's a rational reason for the cryptic first, required, > >> <Directory> entry but I don't know it :) > >> > >> Neil > >> > >> ________________________________ > >> From: [EMAIL PROTECTED] [ > >> [EMAIL PROTECTED] On Behalf Of Chris Mumford [ > >> [EMAIL PROTECTED] > >> Sent: Sunday, June 08, 2008 5:42 PM > >> To: General discussion for Windows Installer XML toolset. > >> Subject: [WiX-users] Source vs. target > >> > >> I'm ashamedly naive about a fairly core issue with WiX. Maybe you guys > can > >> clear this up for me. As I write my installer I've been thinking of the > >> "source" files as those that I am installing, and the "target" as where > >> they > >> will be on the machine on which the install is being run. > >> > >> So right away I'm looking at the first directory element in my *.wxs > file: > >> > >> <Directory Id="TARGETDIR" Name="SourceDir"> > >> and I'm having a hard time figuring out what the heck this even means. > The > >> MSDN documetation for > >> SourceDir<http://msdn.microsoft.com/en-us/library/aa371857(VS.85).aspx > >> >just > >> says, "The > >> *SourceDir* property is the root directory that contains the source > cabinet > >> file or the source file tree of the installation package". Now since I > >> never > >> create or see a cabinet file when running WiX I'm assuming that this is > the > >> directory containing my MSI file when running the installation. But when > I > >> run the installation it's set to drive C:\ weven though my MSI is on a > >> network share. > >> > >> -Chris > >> > ------------------------------------------------------------------------- > >> Check out the new SourceForge.net Marketplace. > >> It's the best place to buy or sell services for > >> just about anything Open Source. > >> http://sourceforge.net/services/buy/index.php > >> _______________________________________________ > >> WiX-users mailing list > >> WiX-users@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/wix-users > >> > ------------------------------------------------------------------------- > >> Check out the new SourceForge.net Marketplace. > >> It's the best place to buy or sell services for > >> just about anything Open Source. > >> http://sourceforge.net/services/buy/index.php > >> _______________________________________________ > >> WiX-users mailing list > >> WiX-users@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/wix-users > >> > > ------------------------------------------------------------------------- > > Check out the new SourceForge.net Marketplace. > > It's the best place to buy or sell services for > > just about anything Open Source. > > http://sourceforge.net/services/buy/index.php > > _______________________________________________ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
