I've noticed a couple things I wonder about:
Let say I use:
Source="$(env.WINDIR)\notepad.exe
The wixlib gets formatted as C:\WINDOWS\NOTEPAD.EXE.
If I type the file name wrong, it still compiles with no errors. It's not
until I consume the library in a merge module that it reports a failure.
Our current build process has dozens of service family builds. I plan on
implemnting fragments and libraries in these builds and then consuming the
libraries in downstream builds. I'm concerned that:
1) Incorrect file paths will manifest themselves too late in the process.
2) When using a different variable like $(env.INSTALLFILES) if the directory
path is different for different builds the wixlib is already formatted and the
files won't line up.
Does anyone have any thoughts on this?
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovations from Sun and the OpenSource community. Download a copy and
enjoy capabilities such as Networking, Storage and Virtualization.
Go to: http://p.sf.net/sfu/opensolaris-get
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
