One thing to consider is making it granular such that if you later patch you can patch more granular resources. If you refer to one Component, for example, everything in that fragment is pulled in. So put each component in a separate fragment. Group custom actions and their binary (if binary CAs) into separate fragments. Even put the ProductVersion property in a separate fragment so that you can use author a patch family to update the ProductVersion or not (constituting a minor upgrade patch if ProductVersion changes).
Stas Klyachkovsky wrote: > > Hi there, > > I’ve decompiled my IS MSI and now I have one big .wxs file, which I > want to fragment. > > Before I start, I want to gather WiX design best practice. Could > somebody share or recommend any resources? > > Thanks, > > Stas > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > ------------------------------------------------------------------------ > > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Heath Stewart Deployment Technology Group, Microsoft http://blogs.msdn.com/heaths ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
