Hello again all, I'm back sooner than I thought I would be, with a reference counting issue. Imagine you had a software product, you release new versions every 6 months so customers frequently run previous versions of the software with current versions. Imagine now that you installed version 1.0 then version 2.0. Now 1.0 is no longer needed so you uninstall 1.0 but it takes components with it that are still in use by 2.0. These components have the SharedDllRefCount set to yes, they have the same guid as the newer version to. I am unsure if this is wise or not but changing the guid doesn't seem to have changed the outcome.
If we run the scenario is a more sensible order it works though. Install 1.0, install 2.0, remove 2.0, common component is left. I have the logs and I'm about to dig through them but I thought I'd quickly fire this off incase there is something simple I'm missing here. Kind regards Simon The information contained in this e-mail is likely to be confidential and may be legally privileged. It is intended only for the addressee. If you have received this message in error please notify the sender immediately at the above address. The disclosure, copying or distribution of this message or its contents without the prior approval of Wallingford Software is strictly prohibited. Wallingford Software is not liable for unauthorised disclosures nor for subsequent actions or omissions in reliance upon them. Registered in the UK, company no: 02288719 Wallingford Software Limited, Howbery Park, Wallingford, Oxfordshire, OX10 8BA ------------------------------------------------------------------------- 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
