What Blair highlights below is probably the best misunderstood feature of wixlib/shared fragments - you can reference *.wxs and *.wixobj each time you build, but only the fragments that are referenced are included in the MSI output.
Meaning you can have a large number of fragments in your common/shared directory, and your "main" project just needs to make appropriate use of ComponentRef, ComponentGroupRef, CustomActionRef, UIRef, etc. You can have fragments as big or as small as you like and one reference pulls in the whole component. (nested ComponentGroupRef's come in handy as well) Note that if if your setup takes a long time to compile, and/or the shared components rarely change then it is probably better to use wixlibs - my setup compiles very quickly so I'm happy to recompile everything each time. Sascha > One other thing superior with the wixlib/shared fragments approach over the > MSM one is that any fragments you don't access in some way aren't included > in the final link, meaning they don't take up any room in your MSI. That > means you can always include all of them in all your projects, and just > reference what you need. Merge modules, once built, are an all-or-nothing > where simply including them includes everything in the MSM in your MSI, > whether you really needed it or not. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
