Hi Rafi, If you're primarily using WiX for all your installs, using compone...@guid='*'] will cause your component guids to be generated as a hash of the target path... So, provided the target paths line up based on your directory structure in your source, all the GUIDs should come out generated in a similar fashion. I'm sure others here will attest that mismatched component GUIDs now will cause you tons more pain down the road.
If you're installing on top of files which may have been installed by another tool using the refcounts found at HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Shared DLLs, you'll probably want to set compone...@shareddllrefcount='yes']. http://wix.sourceforge.net/manual-wix2/wix_xsd_component.htm (PS say hi to your wife and kid for me!) -Erik G. On Tue, Sep 8, 2009 at 11:54 PM, Rafael Campana<raficamp...@hotmail.com> wrote: > > Hello, > > Our build system generates two separate .wxs files (and therefore two > installers) dynamically dependent on our deployment directories - think about > it as two products/installers that can run independently, but can 'talk' to > each other. > By default, both of these installers install into the same directory, and a > number of the files are "shared" between the two installers. > > The problem is that after installing the two, and then uninstalling one of > them leaves the left over installation crippled because it removes more files > than what it should - almost like the ref count was wrong, but I think what's > happening is that when installer #2 comes along, sees that the "shared" files > are already there, then it just does not install them, and not incrementing > the ref count on them. > > It looks like the only way to make it work is to group these "shared" files > into one component, and make sure both .wxs files have the same GUID for the > "shared" component. Is this really the only way you can make it work? Can > you suggest another way of handling a case like this? Any way of making it > work with separate component GUIDs? > How do files that may be installed in the System32 work with WiX? or WiX > installers/products that place files in C:\Program Files\Common Files ? > > Thank you for helping! > > > _________________________________________________________________ > Windows Live: Make it easier for your friends to see what you’re up to on > Facebook. > http://windowslive.com/Campaign/SocialNetworking?ocid=PID23285::T:WLMTAGL:ON:WL:en-US:SI_SB_facebook:082009 > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
