Re: [WiX-users] Installation on Vista
Hi Bob, Thank your for pointing this out and helping me to clarify things. Cheers Volker Bob Arnson wrote: Volker Enderlein wrote: this way). The installer is started without elevation and defaults to an per-user installation. Later the user/admin can change the preselection in the GUI to an per-machine installation. And if he presses the install button Vista UAC prompts for elevation. All I do is set the ALLUSERS Property for a per-user installation to {} and for a per-machine installation to 1. When running without GUI it defaults to 2. Vista always starts packages without elevation. Unless you use Package/@InstallPrivileges=limited or Package/@InstallScope=perUser MSI will prompt for elevation when the user clicks the final Install button that kicks off the installation. That's regardless of the ALLUSERS value. -- Volker Enderlein Tel: +49 (0)371 53119651 Institut für Mechatronik Fax: +49 (0)371 53119699 Reichenhainer Strasse 88 email: [EMAIL PROTECTED] D-09126 Chemnitz - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Installation on Vista
Hi, I want my wix based installer to run on windows 2000, XP, and Vista. It should offer a per-user and per-machine installation. Now I read in a previous task an answer from Bob Arnson that it's not possible under Windows Vista to request elevation at run time. But my first tests on a vista machine yield an opposite result (or at least I am interpreting it this way). The installer is started without elevation and defaults to an per-user installation. Later the user/admin can change the preselection in the GUI to an per-machine installation. And if he presses the install button Vista UAC prompts for elevation. All I do is set the ALLUSERS Property for a per-user installation to {} and for a per-machine installation to 1. When running without GUI it defaults to 2. Can someone provide me additional facts for this issue? Thanks in advance, Cheers Volker -- Volker Enderlein Tel: +49 (0)371 53119651 Institut für Mechatronik Fax: +49 (0)371 53119699 Reichenhainer Strasse 88 email: [EMAIL PROTECTED] D-09126 Chemnitz - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installation on Vista
Ok, I just read further and it seems that the behaviour is related to the setting of the ALLUSERS property. I is explained in detail in http://msdn.microsoft.com/en-us/library/aa371865(VS.85).aspx Cheers Volker Volker Enderlein wrote: Hi, I want my wix based installer to run on windows 2000, XP, and Vista. It should offer a per-user and per-machine installation. Now I read in a previous task an answer from Bob Arnson that it's not possible under Windows Vista to request elevation at run time. But my first tests on a vista machine yield an opposite result (or at least I am interpreting it this way). The installer is started without elevation and defaults to an per-user installation. Later the user/admin can change the preselection in the GUI to an per-machine installation. And if he presses the install button Vista UAC prompts for elevation. All I do is set the ALLUSERS Property for a per-user installation to {} and for a per-machine installation to 1. When running without GUI it defaults to 2. Can someone provide me additional facts for this issue? Thanks in advance, Cheers Volker -- Volker Enderlein Tel: +49 (0)371 53119651 Institut für Mechatronik Fax: +49 (0)371 53119699 Reichenhainer Strasse 88 email: [EMAIL PROTECTED] D-09126 Chemnitz - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] light.exe crash when using Shortcuts and Merge modules in Wix
Hi folks, I'm using WiX 2.0.5805.0 on Windows XP and facing a crash of light.exe when using Merge Modules and Shortcuts together. If I omit the Shortcut definition everything runs fine. The error message from light.exe is: light.exe : error LGHT0001 : Beim Aufruf einer COM-Komponente wurde ein HRESULT E_FAIL-Fehler zurückgegeben. Exception Type: System.Runtime.InteropServices.COMException Stack Trace: bei Microsoft.Tools.WindowsInstallerXml.IMsmMerge2.Merge(String feature, String directory) bei Microsoft.Tools.WindowsInstallerXml.Binder.MergeModules(String databasePath, Output output) bei Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output) bei Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) You'll find the simple test program to reproduce this behaviour attached. test.wxs ?xml version=1.0 encoding=windows-1252? Wix xmlns=http://schemas.microsoft.com/wix/2003/01/wi; Product Name=alaska 5.2 Id=A6FD86D1-28AD-4387-B90A-EEB241E7F002 Language=1033 Codepage=1252 Version=5.2.0 Manufacturer=Institute of Mechatronics Package Id=---- Keywords=Installer Description=Test Installer Comments=alaska is a registered trademark of Institute of Mechatronics. Manufacturer=Institute of Mechatronics InstallerVersion=100 Languages=1033 Compressed=yes SummaryCodepage=1252 / Condition Message=You need to be an administrator to install this product. Privileged /Condition Media Id=1 Cabinet=Sample.cab EmbedCab=yes DiskPrompt=CD-ROM #1 / Property Id=DiskPrompt Value=Test 1.0 Installation [1] / Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Name=PFiles Directory Id=IfmFolder Name=Test Directory Id=INSTALLDIR Name=alaska LongName=Test 1.0 Merge Id=VC_User_MFC71_Loc.3B4432BE_1CFD_4D42_9C85_9C9C551C257A Language=1033 SourceFile=C:\Programme\Gemeinsame Dateien\Merge Modules\VC_User_MFC71_Loc_RTL_X86_---.msm DiskId=1 / Directory Id=Compositing Name=Composit LongName=Compositing Component Id=Test_01 Guid=47EB0E1F-FE57-4953-8E70-2EBCA174A98A File Id=TestEXE Name=Test.exe LongName=Test.exe DiskId=1 Source=Test.exe Vital=yes Shortcut Id=startmenuTest Directory=ProgramMenuDir Name=Test LongName=Test 1.0 WorkingDirectory=Compositing Icon=Test.exe IconIndex=0 / /File /Component /Directory /Directory /Directory /Directory Directory Id=ProgramMenuFolder Name=PMenu LongName=Programs Directory Id=ProgramMenuDir Name=alaska LongName=Test 1.0 / /Directory /Directory Feature Id=Compositing Title=Compositing Module Description=The Compositing Module ConfigurableDirectory=INSTALLDIR Level=1000 ComponentRef Id=Test_01 / MergeRef Id=VC_User_MFC71_Loc.3B4432BE_1CFD_4D42_9C85_9C9C551C257A / /Feature UIRef Id=WixUI_Mondo / UIRef Id=WixUI_ErrorProgressText / Icon Id=Test.exe SourceFile=Test.exe / /Product /Wix Hope someone could shed light on this issue (pun intended). Cheers Volker -- Volker Enderlein Tel: +49 (0)371 53119651 Institut für Mechatronik Fax: +49 (0)371 53119699 Reichenhainer Strasse 88 email: [EMAIL PROTECTED] D-09126 Chemnitz - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] light.exe crash when using Shortcuts and Merge modules in Wix
That did the trick. It also fixed my problems with Shortcuts installing from merge modules. I would not have thought it to be that easy. Thank you for your immediate response and your wonderful WiX toolkit! I enjoy working with it. Keep up the good work, Cheers Volker Rob Mensching schrieb: Can you try grabbing the mergemod.dll out of the latest drop of the WiX v3 toolset (http://wix.sourceforge.net/releases)? There was a bug recently found in mergemod.dll that the VC runtime merge modules seem to have uncovered. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Volker Enderlein Sent: Friday, June 06, 2008 02:33 To: wix-users@lists.sourceforge.net Subject: [WiX-users] light.exe crash when using Shortcuts and Merge modules in Wix Hi folks, I'm using WiX 2.0.5805.0 on Windows XP and facing a crash of light.exe when using Merge Modules and Shortcuts together. If I omit the Shortcut definition everything runs fine. The error message from light.exe is: light.exe : error LGHT0001 : Beim Aufruf einer COM-Komponente wurde ein HRESULT E_FAIL-Fehler zurückgegeben. Exception Type: System.Runtime.InteropServices.COMException Stack Trace: bei Microsoft.Tools.WindowsInstallerXml.IMsmMerge2.Merge(String feature, String directory) bei Microsoft.Tools.WindowsInstallerXml.Binder.MergeModules(String databasePath, Output output) bei Microsoft.Tools.WindowsInstallerXml.Binder.Bind(Output output) bei Microsoft.Tools.WindowsInstallerXml.Tools.Light.Run(String[] args) You'll find the simple test program to reproduce this behaviour attached. test.wxs ?xml version=1.0 encoding=windows-1252? Wix xmlns=http://schemas.microsoft.com/wix/2003/01/wi; Product Name=alaska 5.2 Id=A6FD86D1-28AD-4387-B90A-EEB241E7F002 Language=1033 Codepage=1252 Version=5.2.0 Manufacturer=Institute of Mechatronics Package Id=---- Keywords=Installer Description=Test Installer Comments=alaska is a registered trademark of Institute of Mechatronics. Manufacturer=Institute of Mechatronics InstallerVersion=100 Languages=1033 Compressed=yes SummaryCodepage=1252 / Condition Message=You need to be an administrator to install this product. Privileged /Condition Media Id=1 Cabinet=Sample.cab EmbedCab=yes DiskPrompt=CD-ROM #1 / Property Id=DiskPrompt Value=Test 1.0 Installation [1] / Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Name=PFiles Directory Id=IfmFolder Name=Test Directory Id=INSTALLDIR Name=alaska LongName=Test 1.0 Merge Id=VC_User_MFC71_Loc.3B4432BE_1CFD_4D42_9C85_9C9C551C257A Language=1033 SourceFile=C:\Programme\Gemeinsame Dateien\Merge Modules\VC_User_MFC71_Loc_RTL_X86_---.msm DiskId=1 / Directory Id=Compositing Name=Composit LongName=Compositing Component Id=Test_01 Guid=47EB0E1F-FE57-4953-8E70-2EBCA174A98A File Id=TestEXE Name=Test.exe LongName=Test.exe DiskId=1 Source=Test.exe Vital=yes Shortcut Id=startmenuTest Directory=ProgramMenuDir Name=Test LongName=Test 1.0 WorkingDirectory=Compositing Icon=Test.exe IconIndex=0 / /File /Component /Directory /Directory /Directory /Directory Directory Id=ProgramMenuFolder Name=PMenu LongName=Programs Directory Id=ProgramMenuDir Name=alaska LongName=Test 1.0 / /Directory /Directory Feature Id=Compositing Title=Compositing Module Description=The Compositing Module ConfigurableDirectory=INSTALLDIR Level=1000 ComponentRef Id=Test_01 / MergeRef Id=VC_User_MFC71_Loc.3B4432BE_1CFD_4D42_9C85_9C9C551C257A / /Feature UIRef Id=WixUI_Mondo / UIRef Id=WixUI_ErrorProgressText / Icon Id=Test.exe SourceFile=Test.exe / /Product /Wix Hope someone could shed light on this issue (pun intended). Cheers Volker -- Volker Enderlein Tel: +49 (0)371 53119651 Institut für Mechatronik Fax: +49 (0)371 53119699 Reichenhainer Strasse 88 email: [EMAIL PROTECTED] D-09126 Chemnitz - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net
Re: [WiX-users] How to make the ProgramMenuDir configurable?
Bob Arnson schrieb: Volker Enderlein wrote: i came across the idea of making the ProgramMenuDir configurable as InstallShield and other installers do. You can give a different name to the program group. Is that possible in WiX and if yes how? Create a subdirectory of ProgramMenuFolder and you can give it any name you want. Thanks for your answer Bob, but I think I need to clarify the difficulties I am facing. I know how to place a directory under the ProgramMenuFolder like Directory Id=ProgramMenuFolder Name=PFiles LongNamePrograms Directory Id=ProgramMenuDir Name=test LongName=Test 1.0 / /Directory But say I have a property GROUPSEL which has been set in a UIDialog and want to use this name. How would I do that? Directory Id=ProgramMenuFolder Name=PMenu LongNamePrograms !-- does not work -- Directory Id=ProgramMenuDir Name=test LongName=[GROUPSEL] / !-- does not work -- Directory Id=ProgramMenuDir Name=test LongName=GROUPSEL / !-- how to formulate it properly? -- Directory Id=ProgramMenuDir Name=test LongName= / /Directory I searched the archives and the help manual, but don't find a properly solution. Maybe it's simply related using the wrong keywords. Thank you, Cheers Volker -- Volker Enderlein Institut für Mechatronik e.V. an der Tel: +49 (0)371 53119651 Technischen Universität Chemnitz Fax: +49 (0)371 53119699 Reichenhainer Strasse 88 email: [EMAIL PROTECTED] D-09126 Chemnitz - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to make the ProgramMenuDir configurable?
Volker Enderlein schrieb: Bob Arnson schrieb: Volker Enderlein wrote: i came across the idea of making the ProgramMenuDir configurable as InstallShield and other installers do. You can give a different name to the program group. Is that possible in WiX and if yes how? Create a subdirectory of ProgramMenuFolder and you can give it any name you want. Thanks for your answer Bob, but I think I need to clarify the difficulties I am facing. I know how to place a directory under the ProgramMenuFolder like Directory Id=ProgramMenuFolder Name=PFiles LongNamePrograms Directory Id=ProgramMenuDir Name=test LongName=Test 1.0 / /Directory But say I have a property GROUPSEL which has been set in a UIDialog and want to use this name. How would I do that? Directory Id=ProgramMenuFolder Name=PMenu LongNamePrograms !-- does not work -- Directory Id=ProgramMenuDir Name=test LongName=[GROUPSEL] / !-- does not work -- Directory Id=ProgramMenuDir Name=test LongName=GROUPSEL / !-- how to formulate it properly? -- Directory Id=ProgramMenuDir Name=test LongName= / /Directory I searched the archives and the help manual, but don't find a properly solution. Maybe it's simply related using the wrong keywords. Thank you, Cheers Volker I knew I was missing some fundamentals of WiX. I found the answer reading the wix tutorial a second time more carefully. CustomAction Id='PropertyAssign' Directory='INSTALLDIR' Value='[TARGETDIR]\Program Files\Acme\Foobar 1.0\bin' / should do the trick. Thanks agaín for your answer. Keep up the good work, Cheers Volker -- Volker Enderlein Institut für Mechatronik e.V. an der Tel: +49 (0)371 53119651 Technischen Universität Chemnitz Fax: +49 (0)371 53119699 Reichenhainer Strasse 88 email: [EMAIL PROTECTED] D-09126 Chemnitz - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users