Hey Randall, The "SourceDir\" is by design. Inside a .wixproj file you can set the <BaseInputPaths> MSBuild property to the root directory. This directory will then be replaced by "SourceDir\".
Hope that helps, Brian Rogers "Intelligence removes complexity." - Me http://icumove.spaces.live.com On Mon, Jun 1, 2009 at 9:54 AM, Randall Carter <racar...@teleflora.com>wrote: > Hi all, > > I have a TFS build process that packages the build outputs with WiX tool > set. The Team Build scripts runs nightly and use a VS solution which > includes one or more Visual Studio applications or libraries and a WiX > project. The WiX project has a single Product.wxs file that is nothing more > than a place holder with a reference in it to one or more ComponentGroupRef > elements, each ComponentGroupRef is designed to match fragments that are > created during the build process . Recently I have come up against a problem > on a web portal application that has a deep path for the individual portal > apps, this long path is giving me fits harvesting it, so I can setup an > administrative deployment for our automated deployment process. > > At the end of a Team Build script the last target collects the deployable > files, content, binaries and so on, copies them to a folder, cleans them up > and readies them for packaging, this includes laying out the directory > structure that mirrors the target deployment platform. I then harvest a dir > fragment from a full path that looks something like: > P:\WebPup\Click2Call\Click2CallAdmin\Dev\Click2CallAdmin\DEV_Deploy_C2CAdm_v1.0.92.1\Inetpub\InternalPortal\InternalApps\Click2CallAdmin > with Heat using the following syntax: "Heat.exe dir Inetpub -cg > Click2CallFrag -gg -sfrag -ke -template:Fragment -out Click2CallFrag.wxs > .\Inetpub" all of this works great for buiiding a fragment that is included > in my Product.wxs file by ComponentGroupRef, with one exception. > > Each file element looks like this: <File > Id="fil52976F518E1186CF0CFFC7C55BC6FB65" KeyPath="yes" > Source="SourceDir\InternalPortal\InternalApps\Click2CallAdmin\EditPlayFile.aspx" > /> > > The Source property does not have the full path of the item to package, and > no matter what I do, I cannot loose the "SourceDir\" string at the start of > every path, therefore I get an error when it comes time to link each file > into the MSI. I have tried various combinations to get the full path or > virtual path into the Source property so the files can be found but keep > coming up short. Can anyone offer some guidance on how to get a functional > path into the Source property of each File element or get Heat to build a > directory element that recognizes this abreviated path as a functional file > source. > > Thanks, > > Randall Carter > > ------------------------------------------------------------------------------ > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > is a gathering of tech-side developers & brand creativity professionals. > Meet > the minds behind Google Creative Lab, Visual Complexity, Processing, & > iPhoneDevCamp as they present alongside digital heavyweights like Barbarian > Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
