Yeah, that's a weird behavior of Windows Installer. If your Package is
compressed but the File is not compressed, Windows Installer expects the
file in the root of the install (where the .msi file is).

On Tue, Mar 23, 2010 at 8:01 AM, Sanjay Poria <sanjay.po...@xanalys.com>wrote:

> I'm finding that the Directory/@SourceName property seems to have no
> effect. If I define my source files in a fragment as follows (using the
> initial example I gave):
>
> <Media Id='2' Layout='DocFiles' />
>
> <Fragment>
>        <DirectoryRef Id="INSTALLDIR">
>            <Directory Id="dir1234" Name="documents" SourceName="DocFiles">
>                <Component Id="cmpABC" Guid="*">
>                  <File Id="getstartguide" KeyPath="yes" DiskId="2"
> Compressed="no" Source="$(var.DocDir)\doc1.pdf" />
>                 </Component>
>          </DirectoryRef>
> </Fragment>
>
> The installer still tries to find "doc1.pdf" at the same level as the msi
> (instead of in the relative DocFiles\ subdir). Is this some kind of bug?
>
> sanjay
>
> > -----Original Message-----
> > From: Bob Arnson [mailto:b...@joyofsetup.com]
> > Sent: 23 March 2010 02:09
> > Subject: Re: [WiX-users] Installing from embedded CAB file and Folder
> >
> > On 3/22/2010 6:46 PM, Sanjay Poria wrote:
> > > The problem is that when I run the installer, it still expects to
> > find files (doc1, doc2) in the main directory (at the same level as the
> > msi) instead of the "DocFiles" directory. When building, the installer
> > actually creates the source structure as above (which made me think
> > everything was specified ok).
> > >
> >
> > The Layout attribute controls where the files are written, not where
> > they're installed from. For that, use Directory/@SourceName. See also
> > the Directory table in the MSI SDK.
> >
> > --
> > sig://boB
> > http://joyofsetup.com/
> >
> >
>
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>


-- 
virtually, Rob Mensching - http://RobMensching.com LLC
------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to