[WiX-users] Tallow output and incorrect registration absolute path
In WiXv2 tallow's output looks like this: ... After installation in IDE's references I can find registered component, but its registration path is different (C:\WiXSetups\DB\Libs\AttachW.ocx) than real localisation after installation: (C:\Program Files\DB\Libs\AttachW.ocx). I think that is because tallow has placed not relative path in registration information. Is there any way to make registration correct, so that path will change depending on installation localisation. Can I replace that absolute paths with [INSTALLDIR], will it be working? Best regards, Piotr Jaworski - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Re: Microsoft's merge modules problem in WiXv2
For now, tlbinf32 causes build problem, but there is another problem during installation that is caused by: MS VB virtual machine v5: MSVBVM50.7DD453CA-76BD-40F2-8F85-FA7DFA0D244D. If this MM is commented there is no errors during installation. I hope that MSVBVM v6 will be sufficient, but tlbinf32 merge module is still a problem for me now. Best regards, Peter Jaworski On Feb 5, 2008 10:26 AM, Peter Jaworski <[EMAIL PROTECTED]> wrote: > After investigation I have found that form listed below merge modules: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > reported build problem: > > light.exe : error LGHT0001 : Error HRESULT E_FAIL has been returned > from a call to a COM component. > > Exception Type: System.Runtime.InteropServices.COMException > > Stack Trace: > at Microsoft.Tools.WindowsInstallerXml.IMsmMerge2.Merge(String > feature, String directory) > at Microsoft.Tools.WindowsInstallerXml.Binder.MergeModules(String > databasePath, Output output) > at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output) > at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) > > > is connected with tlbinf32 (Microsoft Typelib Information Library)... > How can I handle this problem? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiXv3 (3808): error LGHT0204
What does this error mean: c:\tmp\vqbjy0iu\Libs_file.msi : error LGHT0204 : ICE39: PID_WORDCOUNT value in Summary Information Stream is not valid. Source image flags must be 0, 1, 2, or 3. ? Generally, msi file has been created and installation is going correctly, but it is interesting because of that error... Thanks for any information. 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/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Tallow does not detects EXE registration information
Hello, I have a few EXE files written in VB6 as ActiveX that need to be registered, but tallow does not prepares registration nodes in its output. I am currently using WIXv2. Previously heat, from WiXv3, has prepared registration information for those EXE. Is there any way to force tallow creating those EXE registration nodes in its output? 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/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Handling VB6 COMs in WiXv2.0
> > I see, seems I was on the wrong direction. Sorry, but then I could not > help > you further. > Anyway thank you. > > If your question on VB6 Com support based on discussion regarding > ComplusExtension > http://www.nabble.com/WixComPlusExtension-in-Wix-v3-td14923013.html > then I could state that the ComplusExtension has nothing to do with VB6 > Com > registration. > > So perhaps you might give Wix3 and heat another try in registering your > Com > compontents > Oh, that is a good news, but COM+ are used when for example I would like to use VB6 COMs from .net applications, does it true? Once more thank you. Best regards, Peter Jaworski <http://www.joyofsetup.com/> - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Re: Handling VB6 COMs in WiXv2.0
Thank you for you advices. > > 1)What should I do to make COMs registering? > SelfRegCost="1" is required to perform MSI SelfReg > Source="Libs\AttachW.ocx" SelfRegCost="1" /> > (1 is ok for registry entries it is used for progress bar) Yes, but my question idea was: *How to* invoke tallow to *force* it scanning the directory with COMs and *generating for all* those COMs separate components, for each, in one fragment wxs file, with registration information. I do not want self registration. > Basically adding the com registry information with separate wix registry > entries is the preferred way and > SelfReg should be avoided (search wix-users List for SelfReg) > Heat could also produce the tallow layout when using -scom and/or -sreg > parameters see > http://www.wixwiki.com/index.php?title=Heat Once more: Is VB6 COMs registration supported in WIXv3 for now? Because a few weeks ago I was informed that not, because of some bug. That is why I have moved backward to WiXv2, so* I have* to use that "ugly" * tallow* instead of heat. For now, I am writing tool that scans directory and invokes tallow for all files from directory separately, then it modifies tallow's output (adds feature node, removes warnings, and other things) files and creates merged feature WXS file that contains references to features from those separate fragments' files. This will also allow me not to modify GUIDs for COMs components that are not changed, when generating new setup. Now it looks working registering some example files. Once more, thank you for your suggestions. 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/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Handling VB6 COMs in WiXv2.0
I have used following tallow invocation (from WiX2.0.5805.0): tallow -nologo -1 -d Libs -gg > Libs1.wxs adding -s switch causes error for directory, but I do not want to invoke it for every file separately. 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/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Handling VB6 COMs in WiXv2.0
Hello, I have approximately over 300 VB6 COMs that should be registered. I have tried previously, when using WiXv3, use heat to scan directory with components and produce output WXS file. Because there is currently no support for VB6 COMs in WiXv3 I have moved to WiXv2 and instead I have used tallow. If I compare heat and tallow output WXS files then those produced by heat contains some registration information for COMs. Tallow's output looks like output for no-registering elements, there is no registration information nodes. After build and installation of such setup (where has been used WXS file produced by tallow) COMs are not registered. 1)What should I do to make COMs registering? 2)Should I use heat output WXS file and only modify it so it will cover WiXv2 (generally adding LongName attribute)? 3)Is there any other way to auto generate needed information for so many files? *Tallow output:* *Heat output:* 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/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Re: Microsoft's tlbinf32 merge module problem in WiXv2
After investigation I have found that form listed below merge modules: reported build problem: light.exe : error LGHT0001 : Error HRESULT E_FAIL has been returned from a call to a COM component. Exception Type: System.Runtime.InteropServices.COMException Stack Trace: at Microsoft.Tools.WindowsInstallerXml.IMsmMerge2.Merge(String feature, String directory) at Microsoft.Tools.WindowsInstallerXml.Binder.MergeModules(String databasePath, Output output) at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output) at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) is connected with tlbinf32 (Microsoft Typelib Information Library)... How can I handle this problem? 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/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Microsoft's Merge Modules and COM problem in WiXv2
> > 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/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Microsoft's Merge Modules and COM problem in WiXv2
I have prepared my installation configuration and it has been working until I have added some Microsoft's merge modules: Merge modules are placed in Fragment wxs file: - ... (other merge modules)... In main.wxs file there is: ... ... ... - After build I have received: light.exe : error LGHT0001 : Error HRESULT E_FAIL has been returned from a call to a COM component. Exception Type: System.Runtime.InteropServices.COMException Stack Trace: at Microsoft.Tools.WindowsInstallerXml.IMsmMerge2.Merge(String feature, String directory) at Microsoft.Tools.WindowsInstallerXml.Binder.MergeModules(String databasePath, Output output) at Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output) at Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) What have I done wrong? At this stage there is no other COMs attached. MM's GUIDs are received from MSM file by right_click>Property>Summary. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Click next control event - Prematurely Stopped
> I created DLL in MicroSoft Visual Studio > and the type of file is "Application Extension" Could you give more detailed information. All DLLs are "Application Extension" please describe which project type you have chosen for creating DLL under VS (File>New>Project..>Other Languages>Visual C++; here you will find list of possible projects, which one is yours?). See this: http://www.wixwiki.com/index.php?title=Simple_Custom_Action_Dll, there you have description what type of project to choose for CustomAction DLL. 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/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to link to WiXUIExtension.dll - "Light.exe" exited with code 92
On Jan 24, 2008 4:21 PM, Bob Arnson <[EMAIL PROTECTED]> wrote: > Peter Jaworski wrote: > > I have tried to build some test example setup project to test GUI and > > my CustomActionDLL. I have done something similar to wxs file > > presented at > > http://www.wixwiki.com/index.php?title=Simple_Custom_Action_Dll. > > > > But after build I have gotten in Visual Studio 2005: > > Error 1 "Light.exe" exited with code 92.C:\Program > > Files\MSBuild\Microsoft\WiX\v3.0\Wix.targets 11226 WixSampleDllCA > > > > 92 is a duplicate symbol error. Build outside of VS to get a more > detailed error message. OK, I have solve this error just after sending that e-mail. Thank you for error description. Is there any table with errors' numbers and its descriptions? This "debugging" feature for WiX project under VS is not usefull. I have still problem with WiXUIExtension.dll referencing outside VS (because not using WiX project) and I have to comment lines that are "refered" to WiXUIExtension.dll features to compile it outside VS. How to solve this? Is there any command line attribute for candle or light (both in v2 and v3)? Thank you, ones more for your current 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/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix multiple installs
> The UI part gathers the information from the user and the target system as > usual, then opens the MSI database of the target package, "patches" it with > new GUIDs, starts the main installation as msiexec /I > and silently closes itself. In such case every > time you install your product, from the system point of view it launches a > different MSI package each time. > I'm not sure if it is the way to go for your case and if it's at all the > WiX-like approach. But when I was searching for the solution to this > problem, this is the best advice I managed to get. I have just thought the same, the use of setup bootstrapper that patches the MSI on the fly is, I think, a good solution. Similar as when preparing multilanguage support. As described here: http://www.tramontana.co.hu/wix/lesson9.php. You have to, in some how, modify/change update code so the Windows Installer will think it as a setup of other application and install the same application next to prevously installed. 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/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Click next control event - Prematurely Stopped
> Am using one DLL custom action. > (..) > There is no wrong in dll. Because it is working fine in some OS's. Tell us something more about DLL, especially what kind of DLL is it (MFC, COM, .net...). How it is linked. It may need some runtimes that cause that on some installations it works (because libraries or runtimes are present) and on other it does not Best regards, Piotr Jaworski - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to link to WiXUIExtension.dll - "Light.exe" exited with code 92
Hello, I have tried to build some test example setup project to test GUI and my CustomActionDLL. I have done something similar to wxs file presented at http://www.wixwiki.com/index.php?title=Simple_Custom_Action_Dll. But after build I have gotten in Visual Studio 2005: Error 1 "Light.exe" exited with code 92.C:\Program Files\MSBuild\Microsoft\WiX\v3.0\Wix.targets11226 WixSampleDllCA I have also tried to build in WiXEdit, but unfortunatelly WiXEdit does not use project files and it presents error that are caused by not linked WiXUIExtension.dll. How to force WiXUIExtension.dll linking outside Visual Studio, for example from command line? WiXEdit has much more familiar error presentation than that in VS (where if I click the Wix.targets file is opened instead of pointing the line in wxs file where error is expected - as it is in WiXEdit). 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/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] EnvironmentVariable checking
> >1) Is there any nice pattern how to check if environment variable is set > > and if it does, to asign its value to a property in the same way as > > IniFileSearch or RegistrySearch: > > > >... > > > > > > or it is enough to to just use: > > > > > > [%myenvironmentvariable] > > ? > >2) The same feature "for read" from XML nodes would be useful not just > "for write" to XML support. 3) I have to also read some parametes from INI similar files (for example UDL). I see that IniFileSearch tag supports only INI files from system directory. In this case do I have to prepare own DLL file with needed features to handle those files? 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/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] EnvironmentVariable checking
> Is there any nice pattern how to check if environment variable is set > and if it does, to asign its value to a property in the same way as > IniFileSearch or RegistrySearch: > >... > > > or it is enough to to just use: > > > [%myenvironmentvariable] > ? The same feature "for read" from XML nodes would be useful not just "for write" to XML support. Best regards, Piotr Jaworski - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] EnvironmentVariable checking
Hello, Is there any nice pattern how to check if environment variable is set and if it does, to asign its value to a property in the same way as IniFileSearch or RegistrySearch: ... or it is enough to to just use: [%myenvironmentvariable] ? Thank you, for any information. 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/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixComPlusExtension in Wix v3
> > Why has WixComPlusExtension.dll not been included in the weekly builds since > > a long time ago? > > Is support being dropped? > No, there's an open bug on the build process that it's not working since > we switched to MSBuild. 1) Does it mean that if I would like to use DLLs created under VB6 I should use WiXv2? 2)How much time does it take to fix the bug in WiXv3? 3)Which WiXv3 build number supports COMs correctly? 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/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Multi-language support
1) I am using WiX version 3. I would like to create multi-language setup. The user on the first dialog choose the language from down-drop list and in next step I would like the setup to be localised. In version 3 of WiX the multi-language support has to be done the same way as described at: http://www.tramontana.co.hu/wix/lesson9.php, or currently there is much better way, so that I will not need to produce any intermediate transformation file? 2) I have also translation, for my application, placed in access database file. In one of the table I have default country number that define what language should be used as default for application. Can I modify its field using standard SQL support in WiX (as described at: http://www.tramontana.co.hu/wix/lesson7.php (but I am using version 3)), depending on chosen language? Best regards, Piotr Jaworski - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
