Re: [WiX-users] Burn UI
If you dislike the CustomerInformation dialog, then turn it off. You can do it with two clicks: Step 1: Click the Project Assistant Tab Step 2: Click No on "Do you want to prompt users to enter their Company Name and User Name?" There is no one optimal UI experience for every installer in the world. The key is to create easily implemnted variation points to meet a variety of needs. InstallShield actually does this quite well except most people don't bother how to learn how use the tool correctly. From: "Tobias S" Sent: Thursday, October 27, 2011 3:43 PM To: "General discussion for Windows Installer XML toolset." Subject: Re: [WiX-users] Burn UI Personally I think installers should act like the VS2011 one or Burn UI: - First dialog for targetdir + license agreement accept -> then enable install button - Second installing and then either switch to success / failure on second dialog or show a third one with success / failure. To be hones I hate credentials that are nowhere used like e.g. the dialog asking for CompanyName + UserName in InstallShield MSI UIs. -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn UI
Personally I think installers should act like the VS2011 one or Burn UI: - First dialog for targetdir + license agreement accept -> then enable install button - Second installing and then either switch to success / failure on second dialog or show a third one with success / failure. To be hones I hate credentials that are nowhere used like e.g. the dialog asking for CompanyName + UserName in InstallShield MSI UIs. -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Windows Installer won't remove existing during upgrade
You may need to look at the log more carefully. If the uninstall of the older version failed it will roll back and reinstall, and that will leave you with both products installed. That's the issue with RemoveExistingProducts -after- InstallFinalize where it's outside the transacted part of the install. Phil Wilson -Original Message- From: Tim Walters [mailto:rea...@gmail.com] Sent: Thursday, October 27, 2011 1:14 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Windows Installer won't remove existing during upgrade I'm trying to properly implement an upgrade (minor version number change which should trigger a replace). However, Windows Installer leaves older versions installed without touching them (Leaves the program files behind and the Uninstall Programs reg entry). I'm using the same upgradecode for all versions and always changing the product and package codes. I've tried to implement this the following way: >From the logs I can see it runs but I don't know it if attempted to do anything: MSI (c) (74:58) [12:32:12:069]: Doing action: FindRelatedProducts Action 12:32:12: FindRelatedProducts. Searching for related applications Action start 12:32:12: FindRelatedProducts. Action ended 12:32:12: FindRelatedProducts. Return value 1. ... DEBUG: Error 2911: Could not remove the folder C:\Config.Msi\. The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2911. The arguments are: C:\Config.Msi\, , MSI (s) (BC:80) [12:32:27:466]: Note: 1: 2318 2: MSI (s) (BC:80) [12:32:27:466]: No System Restore sequence number for this installation. MSI (s) (BC:80) [12:32:27:466]: Unlocking Server MSI (s) (BC:80) [12:32:27:544]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'. Action ended 12:32:27: InstallFinalize. Return value 1. MSI (s) (BC:80) [12:32:27:544]: Doing action: RemoveExistingProducts Action 12:32:27: RemoveExistingProducts. Removing applications Action start 12:32:27: RemoveExistingProducts. Action ended 12:32:27: RemoveExistingProducts. Return value 1. Action ended 12:32:27: INSTALL. Return value 1. -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Windows Installer won't remove existing during upgrade
I'm trying to properly implement an upgrade (minor version number change which should trigger a replace). However, Windows Installer leaves older versions installed without touching them (Leaves the program files behind and the Uninstall Programs reg entry). I'm using the same upgradecode for all versions and always changing the product and package codes. I've tried to implement this the following way: >From the logs I can see it runs but I don't know it if attempted to do anything: MSI (c) (74:58) [12:32:12:069]: Doing action: FindRelatedProducts Action 12:32:12: FindRelatedProducts. Searching for related applications Action start 12:32:12: FindRelatedProducts. Action ended 12:32:12: FindRelatedProducts. Return value 1. ... DEBUG: Error 2911: Could not remove the folder C:\Config.Msi\. The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2911. The arguments are: C:\Config.Msi\, , MSI (s) (BC:80) [12:32:27:466]: Note: 1: 2318 2: MSI (s) (BC:80) [12:32:27:466]: No System Restore sequence number for this installation. MSI (s) (BC:80) [12:32:27:466]: Unlocking Server MSI (s) (BC:80) [12:32:27:544]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'. Action ended 12:32:27: InstallFinalize. Return value 1. MSI (s) (BC:80) [12:32:27:544]: Doing action: RemoveExistingProducts Action 12:32:27: RemoveExistingProducts. Removing applications Action start 12:32:27: RemoveExistingProducts. Action ended 12:32:27: RemoveExistingProducts. Return value 1. Action ended 12:32:27: INSTALL. Return value 1. -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn UI
On 27/10/2011 18:25, Neil Sleightholm wrote: > Out of interest do people think there is a demand for wizard style install? > Personally I still think they are correct approach and I haven't seen a good > alternative yet. I tend to agree. I know Apple don't always do things right, but they still use multi-page wizard applications on OS X for things like installing XCode. -- Bruce Cran -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Get installer final status (return code) from custom action
I don't think you can have the Windows Installer engine report the exit code before it exits back to custom actions in a MSI package before the installation completes. If you are trying to get information after the installation completes and you have PowerShell v2 available to you then you could try the following command: Get-EventLog -LogName Application -Source MsiInstaller -Newest 20 Obviously, you'll want to modify (or skip entirely) the -Newest parameter to your purposes. To learn more about the Get-EventLog cmdlet run the following: Get-Help -Name Get-EventLog -Full Edwin G. Castro Software Developer - Staff Digital Channels Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail > -Original Message- > From: Wilson, Phil [mailto:phil.wil...@invensys.com] > Sent: Thursday, October 27, 2011 10:31 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Get installer final status (return code) from custom > action > > You could write something to monitor or read the Application Event log. > There are MsiInstaller entries created when a product is installed (and I > think > one for failure too). They seem to be event ID 1033, and there's a > ProductCode, result and ProductName in the entry. > > Phil Wilson > > -Original Message- > From: Elanius [mailto:elani...@gmail.com] > Sent: Thursday, October 27, 2011 4:44 AM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Get installer final status (return code) from custom > action > > Hi > > I am working on installer of our product and I got another requirement from > my beloved product manager. > > So I need collect some statistic about installer and main problem is get final > return code of installer. It would be simple task if I had some top level > application which calls installer through MsiInstallProduct but I it is not my > case. I managed to add Custom Actions on positions -1, -2 and -3 in > InstallExecuteSequence so I know if installation ends with success, user exit > or some error. > > But I can not obtain last msi error a mean error code which is normally > returner by API function MsiInstallProduc. It have to be stored somewhere > because in this time (sequence -3) is obvious that installer is finishing with > some error. But question is if it is accessible? > > thanks for any reply, > elanius. > -- > The demand for IT networking professionals continues to grow, and the > demand for specialized networking skills is growing even more rapidly. > Take a complimentary Learning@Cisco Self-Assessment and learn about > Cisco certifications, training, and career opportunities. > http://p.sf.net/sfu/cisco-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > *** Confidentiality Notice: This e-mail, including any associated or attached > files, is intended solely for the individual or entity to which it is > addressed. > This e-mail is confidential and may well also be legally privileged. If you > have > received it in error, you are on notice of its status. Please notify the > sender > immediately by reply e-mail and then delete this message from your system. > Please do not copy it or use it for any purposes, or disclose its contents to > any > other person. This email comes from a division of the Invensys Group, > owned by Invensys plc, which is a company registered in England and Wales > with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X > 7AW (Registered number 166023). For a list of European legal entities within > the Invensys Group, please go to > http://www.invensys.com/en/legal/default.aspx. > > You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail > recept...@invensys.com. This e-mail and any attachments thereto may be > subject to the terms of any agreements between Invensys (and/or its > subsidiaries and affiliates) and the recipient (and/or its subsidiaries and > affiliates). > > > > -- > The demand for IT networking professionals continues to grow, and the > demand for specialized networking skills is growing even more rapidly. > Take a complimentary Learning@Cisco Self-Assessment and learn > about Cisco certifications, training, and career opportunities. > http://p.sf.net/sfu/cisco-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more r
Re: [WiX-users] Get installer final status (return code) from custom action
You could write something to monitor or read the Application Event log. There are MsiInstaller entries created when a product is installed (and I think one for failure too). They seem to be event ID 1033, and there's a ProductCode, result and ProductName in the entry. Phil Wilson -Original Message- From: Elanius [mailto:elani...@gmail.com] Sent: Thursday, October 27, 2011 4:44 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Get installer final status (return code) from custom action Hi I am working on installer of our product and I got another requirement from my beloved product manager. So I need collect some statistic about installer and main problem is get final return code of installer. It would be simple task if I had some top level application which calls installer through MsiInstallProduct but I it is not my case. I managed to add Custom Actions on positions -1, -2 and -3 in InstallExecuteSequence so I know if installation ends with success, user exit or some error. But I can not obtain last msi error a mean error code which is normally returner by API function MsiInstallProduc. It have to be stored somewhere because in this time (sequence -3) is obvious that installer is finishing with some error. But question is if it is accessible? thanks for any reply, elanius. -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn UI
Out of interest do people think there is a demand for wizard style install? Personally I still think they are correct approach and I haven't seen a good alternative yet. Neil -Original Message- From: Bob Arnson [mailto:b...@joyofsetup.com] Sent: 27 October 2011 03:03 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Burn UI On 26-Oct-11 02:46, Neil Sleightholm wrote: > Mainly 2 but to achieve that 1 would be nice. I don't have a problem with > current WiX UIs everyone understands them and they are simple; every attempt > I have seen to replace that simple interface doesn't impress me (the VS 2011 > doesn't look any better in my view). There's definitely room for a "classic" (i.e., wizard-style) BA that's customizable and configurable. Maybe even a commercial one... -- sig://boB http://joyofsetup.com/ -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat: selective harvesting
Or use Paraffin, a tool I wrote to accomplish this exact task: http://www.wintellect.com/CS/blogs/jrobbins/archive/tags/Paraffin/default.aspx Sorry for the shameless plug. :( John Wintellect http://www.wintellect.com +1-877-968-5528 -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Thursday, October 27, 2011 8:44 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] heat: selective harvesting Or sanitise the output from heat before you use it to build your MSI. Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: 27 October 2011 15:36 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] heat: selective harvesting Copy the folder and delete the pdbs... -Original Message- From: Andreas [mailto:andreassand...@gmx.net] Sent: 27 October 2011 15:01 To: wix-users@lists.sourceforge.net Subject: [WiX-users] heat: selective harvesting I have a source directory with a EXE, hundreds of DLLs, and the corresponding PDBs. What is the best way to harvest only the EXE and DLL files? Of course I don't want the PB files in the MSI. -- Andy - - The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ 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. -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat: selective harvesting
Or sanitise the output from heat before you use it to build your MSI. Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: David Watson [mailto:dwat...@sdl.com] Sent: 27 October 2011 15:36 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] heat: selective harvesting Copy the folder and delete the pdbs... -Original Message- From: Andreas [mailto:andreassand...@gmx.net] Sent: 27 October 2011 15:01 To: wix-users@lists.sourceforge.net Subject: [WiX-users] heat: selective harvesting I have a source directory with a EXE, hundreds of DLLs, and the corresponding PDBs. What is the best way to harvest only the EXE and DLL files? Of course I don't want the PB files in the MSI. -- Andy - - The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ 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. -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Configuring the version information in the bootstrapper?
Bruce Cran wrote: > > I was wondering, are there any plans to allow the various version > properties in the WiX bootstrapper to be customised, even if the > developer doesn't want an entry to be created an ARP? Or, is it a > feature that all bootstrapper executables are 'advertised' as having > been created by WiX? > > For example, the following can't be changed at the moment: > > File description: WiX Toolset Bootstrapper > Product name: Windows Installer XML > > It might be nice if a new property could be added to control whether or > not the ARP entry is created for the bootstrapper, while allowing > Manufacturer and Name to still be used to customize the executable > properties. > > -- > Bruce Cran > Agreed. Who would run an exe not knowing these details. Alternatively if there was a way to set ARPSYSTEMCOMPONENT. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Configuring-the-version-information-in-the-bootstrapper-tp6935998p6936665.html Sent from the wix-users mailing list archive at Nabble.com. -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heat: selective harvesting
Copy the folder and delete the pdbs... -Original Message- From: Andreas [mailto:andreassand...@gmx.net] Sent: 27 October 2011 15:01 To: wix-users@lists.sourceforge.net Subject: [WiX-users] heat: selective harvesting I have a source directory with a EXE, hundreds of DLLs, and the corresponding PDBs. What is the best way to harvest only the EXE and DLL files? Of course I don't want the PB files in the MSI. -- Andy - - The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ 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. -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heat: selective harvesting
I have a source directory with a EXE, hundreds of DLLs, and the corresponding PDBs. What is the best way to harvest only the EXE and DLL files? Of course I don't want the PB files in the MSI. -- Andy -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hard-coding a log file location (with Burn?)
I'd need to get OK from legal, and I'd need to remove the "branding" stuff I've added (I customize the bootstrapper for each product including tracking the version number of the contained MSI in the ProductVersion location of the PE header), but I'll see what I can do. -- John M. Cooper -Original Message- From: Lars Augensen [mailto:lars.augen...@confirmit.com] Sent: Thursday, October 27, 2011 3:33 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Hard-coding a log file location (with Burn?) @John: I was considering going the same route, but unfortunately C++ isn't my cup of tea, and I have no idea where to find the necessary includes for compiling... Would it be possible to beg you for the binary of setup.exe? Pretty please with a cherry on top :) - Lars Augensen Deployment Engineer -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: 26. oktober 2011 19:36 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Hard-coding a log file location (with Burn?) Because of the MS Windows Server 2008 behavior of clearing %TEMP% on reboot (which Install and Continuing Development & Support do routinely during testing and training), they insisted that the LOG files be relocated to a location where the OS wouldn't erase them by default. I had to modify the setup.exe C++ to search for FOLDERID_ProgramData, but it's performing satisfactorily for them now. I suspect many of us have similar requirements. Pre-2008, deploying LOG files to %TEMP% made as much sense as anywhere, but a configurable location would help a lot of us out. Regrettably, while it's an approach I favor, passing /log some-path-name.log doesn't seem to have much traction among either managers or the point-and-click crowd. :) -- John M. Cooper -Original Message- From: Adam Kadzban [mailto:mightyshorta...@gmail.com] Sent: Wednesday, October 26, 2011 11:50 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Hard-coding a log file location (with Burn?) I've used IExpress in the past to wrap an MSI in an EXE - this lets you specify a log file location. I've been meaning to take a look at Burn to see if there is a better way to accomplish this - from what Rob says it looks like the only thing to do would be have the bootstrapper app copy the files from the temp folder after the MSI finished. For IExpress, I've got my build scripts kicking that off to package up the MSI based on a Self Extracting Directive file - then another program changing the EXE properties (version, manufacturer, etc). I don't know if it's the best way, but it does work... -Adam On Wed, Oct 26, 2011 at 9:43 AM, Lars Augensen wrote: > Well, that bug is exactly why I need that functionality, so.. what is > the alternate path you are thinking of using? > > - > Lars Augensen > Deployment Engineer > > -Original Message- > From: Rob Mensching [mailto:r...@robmensching.com] > Sent: 26. oktober 2011 16:38 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Hard-coding a log file location (with Burn?) > > Burn logs to %TEMP%, that's not configurable. There is a bug open that > we need to use another path instead of %TEMP% because reboots on > Windows server clear the folder. However, there are no plans to make > the full path of the log file configurable. > > The MsiLogFileLocation sets variables in Burn to all the log files > being generated so that your bootstrapper application can do whatever > it wants with them after they are written. > > On Wed, Oct 26, 2011 at 7:12 AM, Lars Augensen > wrote: > > > Hi everyone, > > I'm trying to get our setup to log to a specific location that is > > not %temp% - per default. > > > > Given that the MsiLogFileLocation property is read-only and cannot > > be used for giving another location, and telling the users to use > > msiexec instead of setup.exe is not doable - do I have to make a > > custom bootstrapper that sends /lvoicewarmupx c:\my.log to msiexec? > > > > I assume this is something I could do with Burn, if someone could > > point me in the direction of a Howto on Burn (I'm still unclear on > > whether or not Burn should be used in a separate project from the > > setup itself, and even what command-lines to use).. Do I then have > > to handle all other commandlines, repair scenarios etc. myself? > > The .chm file isn't totally clear on this as of yet.. > > > > Lars Augensen > > Deployment Engineer > > lars.augen...@confirmit.com | Phone +47 2150 2572> | Mobile +47 > > 40224293 > > > > > > > > -- > > The demand for IT networking professionals continues to > > grow, and the demand for specialized networking skills is growing > > even more rapidly. > > Take a complimentary Learning@Cisco Self-Assessment and learn about > > Cisco certi
Re: [WiX-users] Missing files in http://wix.sourceforge.net/releases/
Whoow didn't read blog about beta and the mailing list very frequently the last days :-) Maybe, if possible updating the link on wix.sourceforge.net would be great ... -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Get installer final status (return code) from custom action
Hi I am working on installer of our product and I got another requirement from my beloved product manager. So I need collect some statistic about installer and main problem is get final return code of installer. It would be simple task if I had some top level application which calls installer through MsiInstallProduct but I it is not my case. I managed to add Custom Actions on positions -1, -2 and -3 in InstallExecuteSequence so I know if installation ends with success, user exit or some error. But I can not obtain last msi error a mean error code which is normally returner by API function MsiInstallProduc. It have to be stored somewhere because in this time (sequence -3) is obvious that installer is finishing with some error. But question is if it is accessible? thanks for any reply, elanius. -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Configuring the version information in the bootstrapper?
I was wondering, are there any plans to allow the various version properties in the WiX bootstrapper to be customised, even if the developer doesn't want an entry to be created an ARP? Or, is it a feature that all bootstrapper executables are 'advertised' as having been created by WiX? For example, the following can't be changed at the moment: File description: WiX Toolset Bootstrapper Product name: Windows Installer XML It might be nice if a new property could be added to control whether or not the ARP entry is created for the bootstrapper, while allowing Manufacturer and Name to still be used to customize the executable properties. -- Bruce Cran -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Missing files in http://wix.sourceforge.net/releases/
Or check out one of the following (unofficial) mirrors: :) http://madbutcher.dyndns.org/snippets/WiX/ http://bluestop.org/wix Albert -Oorspronkelijk bericht- Van: Bob Arnson [mailto:b...@joyofsetup.com] Verzonden: 27 October 2011 04:12 Aan: wix-users@lists.sourceforge.net Onderwerp: Re: [WiX-users] Missing files in http://wix.sourceforge.net/releases/ On 26-Oct-11 16:29, Tobias S wrote: > When having a look at http://wix.sourceforge.net/releases/ it seems > that there exists nothing else than the RSS feeds (No WiX.exe , msi > ...) We won't be putting them on SourceForge any more; SF has a bandwidth quota we were exceeding with all the downloads. The beta build is on Codeplex. -- sig://boB http://joyofsetup.com/ -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Hard-coding a log file location (with Burn?)
@John: I was considering going the same route, but unfortunately C++ isn't my cup of tea, and I have no idea where to find the necessary includes for compiling... Would it be possible to beg you for the binary of setup.exe? Pretty please with a cherry on top :) - Lars Augensen Deployment Engineer -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: 26. oktober 2011 19:36 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Hard-coding a log file location (with Burn?) Because of the MS Windows Server 2008 behavior of clearing %TEMP% on reboot (which Install and Continuing Development & Support do routinely during testing and training), they insisted that the LOG files be relocated to a location where the OS wouldn't erase them by default. I had to modify the setup.exe C++ to search for FOLDERID_ProgramData, but it's performing satisfactorily for them now. I suspect many of us have similar requirements. Pre-2008, deploying LOG files to %TEMP% made as much sense as anywhere, but a configurable location would help a lot of us out. Regrettably, while it's an approach I favor, passing /log some-path-name.log doesn't seem to have much traction among either managers or the point-and-click crowd. :) -- John M. Cooper -Original Message- From: Adam Kadzban [mailto:mightyshorta...@gmail.com] Sent: Wednesday, October 26, 2011 11:50 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Hard-coding a log file location (with Burn?) I've used IExpress in the past to wrap an MSI in an EXE - this lets you specify a log file location. I've been meaning to take a look at Burn to see if there is a better way to accomplish this - from what Rob says it looks like the only thing to do would be have the bootstrapper app copy the files from the temp folder after the MSI finished. For IExpress, I've got my build scripts kicking that off to package up the MSI based on a Self Extracting Directive file - then another program changing the EXE properties (version, manufacturer, etc). I don't know if it's the best way, but it does work... -Adam On Wed, Oct 26, 2011 at 9:43 AM, Lars Augensen wrote: > Well, that bug is exactly why I need that functionality, so.. what is > the alternate path you are thinking of using? > > - > Lars Augensen > Deployment Engineer > > -Original Message- > From: Rob Mensching [mailto:r...@robmensching.com] > Sent: 26. oktober 2011 16:38 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Hard-coding a log file location (with Burn?) > > Burn logs to %TEMP%, that's not configurable. There is a bug open that > we need to use another path instead of %TEMP% because reboots on > Windows server clear the folder. However, there are no plans to make > the full path of the log file configurable. > > The MsiLogFileLocation sets variables in Burn to all the log files > being generated so that your bootstrapper application can do whatever > it wants with them after they are written. > > On Wed, Oct 26, 2011 at 7:12 AM, Lars Augensen > wrote: > > > Hi everyone, > > I'm trying to get our setup to log to a specific location that is > > not %temp% - per default. > > > > Given that the MsiLogFileLocation property is read-only and cannot > > be used for giving another location, and telling the users to use > > msiexec instead of setup.exe is not doable - do I have to make a > > custom bootstrapper that sends /lvoicewarmupx c:\my.log to msiexec? > > > > I assume this is something I could do with Burn, if someone could > > point me in the direction of a Howto on Burn (I'm still unclear on > > whether or not Burn should be used in a separate project from the > > setup itself, and even what command-lines to use).. Do I then have > > to handle all other commandlines, repair scenarios etc. myself? > > The .chm file isn't totally clear on this as of yet.. > > > > Lars Augensen > > Deployment Engineer > > lars.augen...@confirmit.com | Phone +47 2150 2572> | Mobile +47 > > 40224293 > > > > > > > > -- > > The demand for IT networking professionals continues to > > grow, and the demand for specialized networking skills is growing > > even more rapidly. > > Take a complimentary Learning@Cisco Self-Assessment and learn about > > Cisco certifications, training, and career opportunities. > > http://p.sf.net/sfu/cisco-dev2dev > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > -- > virtually, Rob Mensching - http://RobMensching.com LLC > > -- > The demand for IT networking professionals continues to grow, > and the demand for specialized networking skills is growing ev
Re: [WiX-users] Dialog Custom Action always cause installation to fail
Why not use a launch Condition ? The functionality is built into Windows Installer and will respect the UI level set by the user. If testing the prerequisite is too complicated to be handled with regSearch/fileSearch/etc, keep the custom action but have it set a property based on the results. Test the property in the condition. -Original Message- From: Deepa Choundappan [mailto:deepa...@gmail.com] Sent: 27 October 2011 02:04 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Dialog Custom Action always cause installation to fail Hi - We have a Dialog that shows up when a pre req has not been met - the only button on this Dialog is an "Exit" button that then causes the installation to stop when clicked. The problem is in a quiet installation when it looks like this Action is called but exits with a return code of 1. How do I configure this so that everytime this custom action is called - the return code from this action is always set to an error ? -- Thanks ! - - The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ 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. -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Scenario of merge module replacing old non MSI installer.
Hi, I'm fairly new to WiX and have an installation scenario which I could do with some help on: I'm writing a new merge module for a package of shared components that previously had been installed using an ancient version of Installshield (not MSI based). When a new application gets installed which uses this new merge module I need that merge module to find out if the old version of the shared components were installed (that is the Installsheild based stuff) and if so: 1) Uninstall it 2) Install the new shared components BUT it is essential that when the new app is uninstalled it leaves the shared components on as the presence of the old version means that some other application is already installed that relies on the them. Here's an example scenario that consists of the following components: O: Old Installshield based installer for shared components. A: Old application that installed shared components O. M; New merge module for newer versions of shared components that previously were installed using Z. B: New application which includes merge module M 1. User installs application A which also results in shared components O being installed. 2. User installs application B. 3. User uninstalls application B. Application A must still work, so shared components M (installed by B) must not have been removed. Any ideas on how I can achieve this with Wix? Thanks -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
