Re: [WiX-users] WixToolPath variable
Instead of using the WixToolPath variable I found that I can use the WIX environment variable. I set my additional linker options to: -ext WixDifxAppExtension -ext WixUIExtension $(WIX)bin\difxapp_x86.wixlib This works like a charm. - Kim -- *Kim Gybels Software Developer * kim.gyb...@metris.com mailto:kim.gyb...@metris.com Tel: +32 16 74 01 01 Fax: +32 16 74 01 02 * Metris Europe * Interleuvenlaan 86 3001 Leuven Belgium www.metris.com http://www.metris.com/ This message and any attachment are privileged, confidential and contain private information. If you are not the addressee named above any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is prohibited. If you have received this transmission in error, please notify the sender immediately and destroy this e-mail. Metris does not guarantee that the integrity of this communication has been maintained or that this communication is free of viruses, interceptions or interference, and shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Incoming and outgoing email communications may be monitored by Metris, as permitted by applicable law and regulations. -- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixToolPath variable
That means it wasn't finding the .wixlib. Can you paste the light.exe command line it's running? The light.exe command line does not mention the wixlib, although it is shown in the tree view of my setup project. You can't use WixToolPath in the additional options because that's a property which is evaluated before the target that sets the default WixToolPath value. So all variables get expanded when the property is created and not when the property is referenced? Would it work if the Wix.targets used the new syntax to set the WixToolPath property like so: PropertyGroup WixToolPath$(Registry:SOFTWARE\Microsoft\Windows Installer xml\...@installroot)/WixToolPath /PropertyGroup instead of using an initial target that sets the property using ReadRegistry. - Kim -- *Kim Gybels Software Developer * kim.gyb...@metris.com mailto:kim.gyb...@metris.com Tel: +32 16 74 01 01 Fax: +32 16 74 01 02 * Metris Europe * Interleuvenlaan 86 3001 Leuven Belgium www.metris.com http://www.metris.com/ This message and any attachment are privileged, confidential and contain private information. If you are not the addressee named above any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is prohibited. If you have received this transmission in error, please notify the sender immediately and destroy this e-mail. Metris does not guarantee that the integrity of this communication has been maintained or that this communication is free of viruses, interceptions or interference, and shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Incoming and outgoing email communications may be monitored by Metris, as permitted by applicable law and regulations. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixToolPath variable
Kim Gybels wrote: The light.exe command line does not mention the wixlib, although it is shown in the tree view of my setup project. Check its properties to make sure it's not marked to include in the output. So all variables get expanded when the property is created and not when the property is referenced? Yes. Would it work if the Wix.targets used the new syntax to set the WixToolPath property like so: Maybe. Wix.targets can't use it, because it requires .NET 3.5, but try it in your .wixproj. -- sig://boB http://joyofsetup.com/ -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixToolPath variable
Bob Arnson wrote: Kim Gybels wrote: I have these additional linker options set: -ext WixDifxAppExtension -ext WixUIExtension C:\Program Files\Windows Installer XML v3\bin\difxapp_x86.wixlib You can add those files to your project and avoid using any additional linker options value. That doesn't work, I get the following: Error11Unresolved reference to symbol 'CustomAction:MsiProcessDrivers' in section 'Fragment:'. It also copied the file to my project folder, which I dont want. - Kim -- *Kim Gybels Software Developer * kim.gyb...@metris.com mailto:kim.gyb...@metris.com Tel: +32 16 74 01 01 Fax: +32 16 74 01 02 * Metris Europe * Interleuvenlaan 86 3001 Leuven Belgium www.metris.com http://www.metris.com/ This message and any attachment are privileged, confidential and contain private information. If you are not the addressee named above any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is prohibited. If you have received this transmission in error, please notify the sender immediately and destroy this e-mail. Metris does not guarantee that the integrity of this communication has been maintained or that this communication is free of viruses, interceptions or interference, and shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. Incoming and outgoing email communications may be monitored by Metris, as permitted by applicable law and regulations. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixToolPath variable
Kim Gybels wrote: That doesn't work, I get the following: Error11Unresolved reference to symbol 'CustomAction:MsiProcessDrivers' in section 'Fragment:'. That means it wasn't finding the .wixlib. Can you paste the light.exe command line it's running? You can't use WixToolPath in the additional options because that's a property which is evaluated before the target that sets the default WixToolPath value. -- sig://boB http://joyofsetup.com/ -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WixToolPath variable
Hi, I am having trouble using the WixToolPath variable in my Visual Studio WiX project. I have these additional linker options set: -ext WixDifxAppExtension -ext WixUIExtension C:\Program Files\Windows Installer XML v3\bin\difxapp_x86.wixlib However, I would like to avoid the full installation path to WiX like so: -ext WixDifxAppExtension -ext WixUIExtension $(WixToolPath)difxapp_x86.wixlib This gives me the following error: 9light.exe(0,0): error LGHT0103: The system cannot find the file 'difxapp_x86.wixlib' with type 'Source'. From which I conclude that the variable is empty. However, when I set the BeforeBuild target to output a warning containing the variable: Target Name=BeforeBuild Warning Text=test: $(WixToolPath) / /Target I get the following output: 9D:\svn\kube\Main\KUBE v15\Install\WIX\KUBE_Setup.wixproj(0,0): warning : test: C:\Program Files\Windows Installer XML v3\bin\ Any ideas for getting the variable to work with the additional linker options? - Kim PS: using version 3.0.4805.0 -- *Kim Gybels Software Developer * kim.gyb...@metris.com mailto:kim.gyb...@metris.com Tel: +32 16 74 01 01 Fax: +32 16 74 01 02 * Metris Europe * Interleuvenlaan 86 3001 Leuven Belgium www.metris.com http://www.metris.com/ -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixToolPath variable
Kim Gybels wrote: I have these additional linker options set: -ext WixDifxAppExtension -ext WixUIExtension C:\Program Files\Windows Installer XML v3\bin\difxapp_x86.wixlib You can add those files to your project and avoid using any additional linker options value. -- sig://boB http://joyofsetup.com/ -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
