> > <Merge Id="COMCAT.3207D1B0-80E5-11D2-B95D-006097C4DE24" > You don't need to use the ID.GUID form from the .msm. The Id exists only > to link up the Merge and MergeRef elements.
When I have used simple ID now, but the same problem still exists. I have been using ID.GUID form because of tutorial: http://www.tramontana.co.hu/wix/lesson4.php#4.4 > Which version of WiX does this problem occur with? Please provide the full > version number. WiX: 2.0.5805.0 > Which operating system is the problem happening with? Currently, I am working on WinXP Prof. SP2 > Which Platform SDKs and Windows Installer SDKs do you have installed? (This > might have installed a different version of the merge library.) Windows(R) Server 2003 R2 Platform SDK, and WinInst 3.1 (but I don't think that SDK, just regular redistribuable I guess). > Are the modules read-only? Does it work if you make them writeable? (I don't > know whether this is required, I'm just guessing - I've encountered tools > that open files read/write when reading only was required.) Yes, write is enabled. Files are not protected. > That list of merge modules is... odd. WinHTTP 5.1 is supported on Windows > 2000, Windows XP and Windows Server 2003 and is part of the latest service > packs on all those operating systems. None of them require MDAC 2.5, DCOM95, > OLEAUT32.DLL updates (Windows 2000 came with MDAC 2.5, DCOM95 only applies > to Windows 95) and indeed a lot of the DLLs listed are under System File > Protection on these systems. Did you perhaps pick these dependencies up from > Visual Basic 6's Package & Destroy Wizard? [1] It tended to pick up a > complete dependency tree without regard for what should really be > distributed. You see, I am just moving setup from old InstallShield to WiX and some part of software is using old VB6 components. We have to support this. Merge modules are used by InstallShield configuration of current setup. InstallShield is working on dedicated for that purpose Win2Kprof. We have to support Windows 2000 platform. Currently preparing WiX configuration I have just copied those MM listed in InstallShield configuration to folders on machine where I am preparing WiX-based setups. > I'm not even sure where you got a merge module for WinHTTP 5.1 from, because > the documentation states that the above operating systems (2000 SP3, XP SP1, > Windows Server 2003) are the only way to obtain it, and that a merge module > is *not* available. > (http://msdn2.microsoft.com/en-us/library/aa384086.aspx.) As you see above. > [1] Apologies for bad pun. Too much experience with the result of deploying > a P&DW project (especially one built on a later platform and deployed on an > older one: result = trashed system). Well, so what you suggest to make this old VB6 stuff working after installation. Oh, I see what problems will be there when I will add all our VB6 components... :( Wish it will works... I have started with WiXv3 but I was informed that only WiXv2 supports VB6 COMs now :( so I have moved back to WiXv2. Another problem is that heat have listed all those VB6 COMs with a lot of stuff like registry keys, class lists for DLLs and OCX, but, as I have seen, tallow has just listed those files, without preparing nodes for classes and intefaces present in those files, as any other files, so I fill that there will be problem with registration of that old VB6 stuff. Thank you for help. Best regards, Peter Jaworski ------------------------------------------------------------------------- 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
