1. I personally haven't sat down and thought about all of them. Honestly, the strategies I use come from my days of working in C/C++. WiX works very similarly. If you organize your code well in C/C++ and follow similar organization efforts in WiX, it all works out. Duplicating code across .lib files in C/C++ is a path well known to lead to madness. <smile/>
2. There is a deprecated command-line switch to light called "-ai" which means "allow identical rows". I was told this was a bad idea by the people that actually asked for the feature and that is why it was deprecated. Allow identical rows is a big hammer. It will allow any duplicate rows which may allow duplicate data that you would otherwise want to filter out. Note that when duplicates are being found they don't necessarily map back to a particular Component File or Directory Component or Feature Component structure or anything like that. All that .wxs stuff is shredded into bits and pieces necessary for the linking and binding process. Another option is to make smaller .wixlibs. Admittedly the command-lines start getting longer and you can get "chains of .wixlibs" needing to be passed on the command-line but it does give you a lot of control. It is a little bit of a balancing act to get the right granularity. Stryder Crown wrote: > Do you have any links or places that I could go to read on these strategies? > > I'm reluctant to put everything in one (or two) wixlib's since these are > dll's and exe's that contribute to the overall functionality of several > programs. Can't wix just 'ignore' when a wixlib has a reference to a file > that's already been included? you know? "Hey, I know you, I'd recognize > that guid anywhere..." > > On Tue, May 5, 2009 at 11:50 AM, Rob Mensching <r...@wixtoolset.org> wrote: > > >> Putting the same content in different .wixlibs is going to lead to no >> end of troubles. I don't know the specifics but there are several ways >> to restructure the example below to end up with content only in one >> .wixlib. I highly recommend picking one of those strategies (for >> example, you could put all of the below in one .wixlib that is highly >> Fragmented). >> >> Stryder Crown wrote: >> >>> 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 >>> >>> >> ------------------------------------------------------------------------------ >> 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 >> >> > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
