Steve Baker wrote: > My conclusion from my testing still leads me to believe that in my situation, > at least for files, there shouldn't be any chance of one web application > breaking another even though the component id is the same for two separate > resources. John's statement that ref-counting is scoped at the product code > level reinforces my belief that this will work. > > Is there anything else that I should look into before consolidating these > components into a common library? >
You're dealing with a flavor of shared components. The flavor is that the components live in different directories, which is legal when they're shared by different products. However, the risk is the same with "unflavored" shared components: Their composition must remain immutable or you're in for a world of hurt.<g> -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
