Ok, I'm sure this has been asked here before, but I wasn't able to find the
thread or a resolution...
How does anybody else deal with this situation:
I have several WiX projects that share common dependencies that I'm
compiling into wixlibs for larger projects. I want to ensure that a
compiled wixlib (with the object inside) contains all of it's required
dependencies. I would like to be able to build my wixlibs in just one place
and then include them in other projects (MSI installers) as needed. This
way, when my team updates some dll or exe, I only need to update/change the
related wixlib, and not 3 (or 30) other files. Things start to break down
when I have relative directories (coming out of svn) and WiX sees a file
more than once in the final output. Specifically, WiX won't overlook the
fact that the same file (and guid) has been added more than once. Even
through the directory structure is exactly the same. Is this a bug? or is
there something else I should be doing?
Here's an example of the structure I currently have:
Project 1
- wixlib A
Object 1 needs:
-Component X
-Component Y
Object 2 needs:
-Component Z
Project 2
- wixlib B
Object 3 needs:
-Component X
-Component Z
Project 3
Requires Object 1 and Object 3.
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
