Re: [WiX-users] Std Bootstrapper failed: Error
Now this defect is reproducible on all our tester machines. The weirdest thing it that simple verification of any file, signed with company certificate, on the problem computer repels defect ^^ (signtool.exe verify /pa anySignedFile.exe). I added comment to the defect https://sourceforge.net/tracker/?func=detailaid=3380917group_id=105970atid =642714 https://sourceforge.net/tracker/?func=detailaid=3380917group_id=105970ati d=642714 @Rob you mentioned earlier that problem might be in getting right flags passed to WinVerifyTrust(). Could you please look at http://msdn.microsoft.com/en-us/library/aa382384(v=VS.85).aspx http://msdn.microsoft.com/en-us/library/aa382384(v=VS.85).aspx . They set fdwRevocationChecks = WTD_REVOKE_NONE and dwStateAction = WTD_STATEACTION_IGNORE, which may be not correct but it is said it is enough to verify signature and hash. /pre BR style=font-size:4px; a href = http://www.sdl.com/sdl-vision;img src=http://www.sdl.com/images/email_new_logo.png; alt=www.sdl.com/sdl-vision border=0//a BR font face=arial size=2a href =http://www.sdl.com/sdl-vision; style=color:005740; font-weight: boldwww.sdl.com/sdl-vision/a/font BR BR font face=arial size=1 color=#736F6E bSDL PLC confidential, all rights reserved./b If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us.BR SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207.BR Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. /font -- Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to check the Registry with Bundle?
Custom Actions are an MSI concept so you would need to do your oracle detection and configuration custom action inside a bundled MSI. Alternatively you could write your configuration as a standalone tool and add that to the bundle as a .exe package. -Original Message- From: Tobias S [mailto:tobias.s1...@gmail.com] Sent: 06 September 2011 21:03 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to check the Registry with Bundle? hi, consider http://wix.sourceforge.net/manual-wix3/bundle_define_searches.htm Also posted a sample for VCRedist 2010 detection here: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Specifying-Pre- requisites-with-Burn-tp6751843p6751843.html When doing a versioin compare be aware to use a v prefix like e.g. InstallCondition=(NOT MFC100_Version_x86 = v10.0.40219.1) OR NOT MFC100_Version_x86 Regards Tobias - - Malware Security Report: Protecting Your Business, Customers, and the Bottom Line. Protect your business and customers by understanding the threat from malware and how it can impact your online business. http://www.accelacomm.com/jaw/sfnl/114/51427462/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Strange InstallExecuteSequence errors (ICE27) with WixUI_Advanced
Bob Arnson-6 wrote: WixUI_Advanced is the only dialog set that includes something in InstallExecuteSequence. So it pulls in some values that conflict with the bad sequences from the merge module. If the merge modules alone (without the Advanced UI) don't produce these ICE validation errors, would that mean that there is a deeper issue involving WixUI_Advanced? It seems that simply adding this dialog set shouldn't break a previously correct sequence. I got no ICE27 errors before adding WixUI_Advanced. I'm also curious why WixUI_Advanced needs to put anything in InstallExecuteSequence, where Mondo does not. Both dialog sets allow the same basic functionality. Thanks for the help. - John -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Strange-InstallExecuteSequence-errors-ICE27-with-WixUI-Advanced-tp6755603p6768543.html Sent from the wix-users mailing list archive at Nabble.com. -- Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] APPLICATIONFOLDER vs INSTALLDIR
I like the Advanced UI more than Mondo for most things. It cuts down on clicks and superfluous dialogs for the most common use cases. I'm curious why WixUI_Advanced uses APPLICATIONFOLDER instead of the well-known INSTALLDIR property which Mondo and other popular msi build technologies use? I'm also curious why WixUI_Advanced requires the ApplicationFolderName property. I already set the folder name in the particular Directory element's Name attribute. Mondo does not seem to need an extra property. Is it simply a matter of how the author chose to implement WixUI_Advanced? - John Burak -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/APPLICATIONFOLDER-vs-INSTALLDIR-tp6768732p6768732.html Sent from the wix-users mailing list archive at Nabble.com. -- Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] 64-bit burn?
Hi Everyone, I need to call a unmanaged 64-bit .DLL method from my managed bootstrapper using P/Invoke. As such I am trying to get Wix to compile my setup.exe as a 64-bit executable. I tried editing the .wixproj file changing x86 to x64. This gets Visual Studio to allow me to select the setup project as 64-bit in Configuration Manager. Unfortunately when I attempt to compile the solution I get the following error, Error 26 Could not find a part of the path 'C:\Program Files (x86)\Windows Installer XML v3.6\bin\X64\burn.exe'. light.exe 0 1 I have a feeling I am not going about this the right way. Any suggestions? Thanks, Phil -- Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] APPLICATIONFOLDER vs INSTALLDIR
john.burak wrote: I like the Advanced UI more than Mondo for most things. It cuts down on clicks and superfluous dialogs for the most common use cases. I'm curious why WixUI_Advanced uses APPLICATIONFOLDER instead of the well-known INSTALLDIR property which Mondo and other popular msi build technologies use? I'm also curious why WixUI_Advanced requires the ApplicationFolderName property. I already set the folder name in the particular Directory element's Name attribute. Mondo does not seem to need an extra property. Sorry to answer my own question, but maybe this will help someone else who is curios. I finally figured out how to get the 3.5 source and looked at the Advanced UI source and found this: WixUI_Advanced.wxs wrote: Todo: ... = This set is still in active development. = Future releases are likely to be incompatible. = Future releases are likely to be much easier to use. = Use at your own risk. So I think that probably explains it. :) If I'm wrong and the aforementioned aren't simply because Advanced isn't entirely done in v3.5, then feel free to correct me. - John Burak -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/APPLICATIONFOLDER-vs-INSTALLDIR-tp6768732p6769262.html Sent from the wix-users mailing list archive at Nabble.com. -- Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Downloading and installing optional components
I apologize in advance for asking a vague question. I'm going to make this as precise as I can, but it's still open-ended enough to give Google fits. I'm an almost-complete newb to WiX, but a long-time Python programmer. I'd like to distribute an MSI containing a Python application written using the PySide library. So far I have a WiX-based MSI that works just fine, *so long as* the end-user has already installed Python 2.7 and PySide. I'd like to make the experience a little friendlier on end-users, while still keeping the total download size small -- given a full install of Python 2.7 + PySide comes out to around 50Mb, downloading as-needed seems to be the way to go. Therefore, I'd like to try something like the following: 1. Check which architecture is in use (AMD64 or x86) 2. Check HKLM\PythonCore for the presence of Python 2.7 a. If present, go on to 3 b. If not, download the Python 2.7 MSI for the appropriate architecture and install it 3. Find the Python 2.7 install path from HKLM\Python Core\2.7\InstallPath: check in PYTHONINSTALLPATH\Lib\site-packages for the presence of a directory PySide-1.0.6qt474-py2.7.egg-info a. If present, go on to 4 b. If not, download PySide for the appropriate architecture and install it 4. Ta-da, done. Now, I'm pretty sure that mucking about on my own I can address some of this, particularly checking what architecture is in use, reading registry keys, and so on. However, downloading additional MSI installers (and plain .exe installers, in the case of PySide) and launching them ... well, let's just say my Google searches have been in vain. If anyone has any words of advice (even if it's oh God don't don't no you have no idea what you're doing you fol!), I'd love to hear them. :) Thanks much, y'all! -- Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Downloading and installing optional components
This is exactly what Burn is for in WIX v3.6. That'll keyword will probably get you some really good hits in Bing. wink/ On Wed, Sep 7, 2011 at 3:01 PM, Robert J. Hansen r...@sixdemonbag.orgwrote: I apologize in advance for asking a vague question. I'm going to make this as precise as I can, but it's still open-ended enough to give Google fits. I'm an almost-complete newb to WiX, but a long-time Python programmer. I'd like to distribute an MSI containing a Python application written using the PySide library. So far I have a WiX-based MSI that works just fine, *so long as* the end-user has already installed Python 2.7 and PySide. I'd like to make the experience a little friendlier on end-users, while still keeping the total download size small -- given a full install of Python 2.7 + PySide comes out to around 50Mb, downloading as-needed seems to be the way to go. Therefore, I'd like to try something like the following: 1. Check which architecture is in use (AMD64 or x86) 2. Check HKLM\PythonCore for the presence of Python 2.7 a. If present, go on to 3 b. If not, download the Python 2.7 MSI for the appropriate architecture and install it 3. Find the Python 2.7 install path from HKLM\Python Core\2.7\InstallPath: check in PYTHONINSTALLPATH\Lib\site-packages for the presence of a directory PySide-1.0.6qt474-py2.7.egg-info a. If present, go on to 4 b. If not, download PySide for the appropriate architecture and install it 4. Ta-da, done. Now, I'm pretty sure that mucking about on my own I can address some of this, particularly checking what architecture is in use, reading registry keys, and so on. However, downloading additional MSI installers (and plain .exe installers, in the case of PySide) and launching them ... well, let's just say my Google searches have been in vain. If anyone has any words of advice (even if it's oh God don't don't no you have no idea what you're doing you fol!), I'd love to hear them. :) Thanks much, y'all! -- Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 64-bit burn?
Burn is not available for 64bit yet. It is not as simple as changing a couple settings in configuration manager. The Could not find part of the path is a bug in a recent build of WiX v3.6. 64-bit Bundles (aka: Burn that only runs on 64-bit, not Bundles that install 64-bit stuff) are not yet supported. What DLL only exists on 64-bit? On Wed, Sep 7, 2011 at 10:29 AM, Phil Podlevsky philpodlev...@gmail.comwrote: Hi Everyone, I need to call a unmanaged 64-bit .DLL method from my managed bootstrapper using P/Invoke. As such I am trying to get Wix to compile my setup.exe as a 64-bit executable. I tried editing the .wixproj file changing x86 to x64. This gets Visual Studio to allow me to select the setup project as 64-bit in Configuration Manager. Unfortunately when I attempt to compile the solution I get the following error, Error 26 Could not find a part of the path 'C:\Program Files (x86)\Windows Installer XML v3.6\bin\X64\burn.exe'. light.exe 0 1 I have a feeling I am not going about this the right way. Any suggestions? Thanks, Phil -- Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 64-bit burn?
Thank you for the prompt reply as usual Rob. :) I was doing some stuff with the Windows Embedded 7 Enhanced Write Filter API as part of the installer I am working on and ewfapi.dll is an OS .DLL so it's only 64-bit. I found a nice little workaround by spawning the ewfmgr.exe process. It's not as ideal as an API call but it works. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, September 07, 2011 9:27 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] 64-bit burn? Burn is not available for 64bit yet. It is not as simple as changing a couple settings in configuration manager. The Could not find part of the path is a bug in a recent build of WiX v3.6. 64-bit Bundles (aka: Burn that only runs on 64-bit, not Bundles that install 64-bit stuff) are not yet supported. What DLL only exists on 64-bit? On Wed, Sep 7, 2011 at 10:29 AM, Phil Podlevsky philpodlev...@gmail.comwrote: Hi Everyone, I need to call a unmanaged 64-bit .DLL method from my managed bootstrapper using P/Invoke. As such I am trying to get Wix to compile my setup.exe as a 64-bit executable. I tried editing the .wixproj file changing x86 to x64. This gets Visual Studio to allow me to select the setup project as 64-bit in Configuration Manager. Unfortunately when I attempt to compile the solution I get the following error, Error 26 Could not find a part of the path 'C:\Program Files (x86)\Windows Installer XML v3.6\bin\X64\burn.exe'. light.exe 0 1 I have a feeling I am not going about this the right way. Any suggestions? Thanks, Phil -- Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
