[WiX-users] How to add a custom dialog in uninstall process using Wix
Hi, I want to add a dialog box into my installer's uninstalling process. custom dialog have a check box, which will ask user to delete/keep user setting data of the application. User setting data files usually created in application installation directory after installing the application. Any help would be appreciated. Thanks, Sanjay Rao -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Question about Shared Components and their Key Paths
Hi everybody, we have more products sharing the same shared libraries and I'd like to clarify some things, before I proceed. 1) Shared component between two products using same KeyPath and same Guid. - From earlier discussion I understand this is the proper solution and in my tests everything works perfectly. 2) Shared component between two products using DIFFERENT KeyPaths, but SAME Guid. - I've read http://blogs.msdn.com/heaths/archive/2009/12/21/about-shared-components.aspx , but I don't understand if it is supported solution or just one which works, because it needs to work for compatibility reasons. - How should I solve this issue, if the MSIs are authored to use same KeyPaths, but the user is allowed to change the Target Directory independently for each install? Example: - ProductOne and ProductTwo both use SharedLib.Dll with same Guid; - ProductOne installs the SharedLib.Dll in FolderOne - ProductTwo installs the SharedLib.Dll in FolderTwo 3) Shared component between two products using SAME KeyPaths, but DIFFERENT Guids. - I understand the library would get overwritten using the versioning rules. Will this properly work for uninstalls? I need both products to work when the other gets uninstalled. BTW: For updates we are using Major Upgrades. Thank you for clarification. Ondřej Zarevúcky -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to add a custom dialog in uninstall process using Wix
You may only show dialogs during uninstallation via a custom action, the dialogs from the msi won't be shown. Best regards, Sebastian Brand sebast...@instyler.com Geisenfelder Str. 53a 85053 Ingolstadt, Germany EU VAT ID: DE219712370 Phone: +49 841 4544567 www.instyler.com http://www.instyler.com/ Travel add-in for Outlook http://www.traveladdin.com/ : Add travel and return times to your calendar. Instyler Setup http://www.instyler.com/ : Create WiX-based MSI installations, elegantly. Sebastianbrand.com http://www.sebastianbrand.com/ : blogging about software development, deployment and productivity -Original Message- From: Sanjay Rao [mailto:s...@noida.interrasystems.com] Sent: Thursday, January 07, 2010 10:52 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] How to add a custom dialog in uninstall process using Wix Hi, I want to add a dialog box into my installer's uninstalling process. custom dialog have a check box, which will ask user to delete/keep user setting data of the application. User setting data files usually created in application installation directory after installing the application. Any help would be appreciated. Thanks, Sanjay Rao -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list mailto:WiX-users@lists.sourceforge.net WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to add a custom dialog in uninstall process using Wix
I am not aware, how to show dialogs via custom actions. Please help with some sample code. Thanks Regards, Sanjay Rao Sebastian Brand (Instyler Software) wrote: You may only show dialogs during uninstallation via a custom action, the dialogs from the msi won't be shown. Best regards, Sebastian Brand sebast...@instyler.com Geisenfelder Str. 53a 85053 Ingolstadt, Germany EU VAT ID: DE219712370 Phone: +49 841 4544567 www.instyler.com http://www.instyler.com/ Travel add-in for Outlook http://www.traveladdin.com/ : Add travel and return times to your calendar. Instyler Setup http://www.instyler.com/ : Create WiX-based MSI installations, elegantly. Sebastianbrand.com http://www.sebastianbrand.com/ : blogging about software development, deployment and productivity -Original Message- From: Sanjay Rao [mailto:s...@noida.interrasystems.com] Sent: Thursday, January 07, 2010 10:52 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] How to add a custom dialog in uninstall process using Wix Hi, I want to add a dialog box into my installer's uninstalling process. custom dialog have a check box, which will ask user to delete/keep user setting data of the application. User setting data files usually created in application installation directory after installing the application. Any help would be appreciated. Thanks, Sanjay Rao -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list mailto:WiX-users@lists.sourceforge.net WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix bug when converting class/progID set from advertised=yes to advertised=no?
On 1/7/2010 1:11 AM, Bryan Reich wrote: New member to the community. How do I file a bug? https://sourceforge.net/tracker/?group_id=105970atid=642714 (also linked from http://wix.sourceforge.net/). -- sig://boB http://joyofsetup.com/ -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Building a multi-language msi....
Thanks. On Thu, Jan 7, 2010 at 12:36 AM, Rob Mensching r...@robmensching.com wrote: Fundamentally, yes. You can optimize a bit by building a .wixout at step 3 then running light with a different .wxl to generate each MSI from the .wixout. That'll save some linking time. On Wed, Jan 6, 2010 at 12:50 PM, Tony yellowjacketl...@gmail.com wrote: I think we are doing this right, but I want to be sure as it seems painfully tedious. Here is a high-level sequence of what we are currently doing to build a single msi that supports 8 languages (en-us, 4 euro, Japanese and 2 Chinese scripts)... 1. Compile all component binaries. 2. Build a few wixlibs that contain those components. 3. Build en-us version of msi (including our custom action dll) 4. Copy en-us version of the msi so that it becomes our base msi 5. Build a localized version of the msi (built using the existing en-us version our custom action dll) 6. Create transform file using msitran.exe 7. Merge that transform file into our base msi using wisubstg.vbs 8. Repeat steps 5-7 for remaining 6 languages 9. Specify supported languages in the merged msi using wilangid.vbs The entire process is repeated to generate a x64 version of the msi. Does this seem correct? -- Tony -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Tony -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] HELP ...
I am setting up CI utilizing CCNet and MSBuild. I've come to the realization that MSBuild will not work with a Web Deployment Project (vdproj) to create an MSI. Therefore, I am attempting to utilize WiX as the intermediary as I do not want to install Visual Studio on the build box. We are developing in VS 2008 and the OS is Windows Server 2008. However, I cannot seem to get Wix installed in this environment. The Windows Installer XML toolset appears in the program files but doesn't work as WiX doesn't appear to be available. I have searched for each of the executables, to no avail. I think I read some documentation that WiX was included in the OS with Windows Server 2008, but I can't be sure as I have scoured so much material for an answer that I may have dreamed it :). It isn't anywhere that I can find, however. Can you please help me? I've spent way too long on this and am behind schedule. Thank you, Jeannie -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Build WiX Solution After Drop
So I created a Wix Solution and added it to my Team Build process as the last solution to build. But I am using source files inside WiX that aren't created until after my solutions have built and deployed... So how do I delay the WiX compile. Specifically my problem is on the AfterDrop target I am deploying SQL Databases that create sql scripts on the fly. I need those scripts to be wrapped into Wix. But the AfterDrop target is called long after my WiX solution built. THanks! The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] HELP ...
candle.exe, light.exe etc are installed by default to C:\Program Files\Windows Installer XML v3\bin Wix isnt distributed with any OS. It was going to be in Visual Studio but this never happened so the only distributions are on the sourceforge project page. -Original Message- From: Jeannie Efird [mailto:jeannie.ef...@theaba.org] Sent: 07 January 2010 15:18 To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] HELP ... I am setting up CI utilizing CCNet and MSBuild. I've come to the realization that MSBuild will not work with a Web Deployment Project (vdproj) to create an MSI. Therefore, I am attempting to utilize WiX as the intermediary as I do not want to install Visual Studio on the build box. We are developing in VS 2008 and the OS is Windows Server 2008. However, I cannot seem to get Wix installed in this environment. The Windows Installer XML toolset appears in the program files but doesn't work as WiX doesn't appear to be available. I have searched for each of the executables, to no avail. I think I read some documentation that WiX was included in the OS with Windows Server 2008, but I can't be sure as I have scoured so much material for an answer that I may have dreamed it :). It isn't anywhere that I can find, however. Can you please help me? I've spent way too long on this and am behind schedule. Thank you, Jeannie -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] HELP ...
What are the exact failures you are seeing? If it is an install failure, can you send along the verbose log file? On Thu, Jan 7, 2010 at 7:17 AM, Jeannie Efird jeannie.ef...@theaba.orgwrote: I am setting up CI utilizing CCNet and MSBuild. I've come to the realization that MSBuild will not work with a Web Deployment Project (vdproj) to create an MSI. Therefore, I am attempting to utilize WiX as the intermediary as I do not want to install Visual Studio on the build box. We are developing in VS 2008 and the OS is Windows Server 2008. However, I cannot seem to get Wix installed in this environment. The Windows Installer XML toolset appears in the program files but doesn't work as WiX doesn't appear to be available. I have searched for each of the executables, to no avail. I think I read some documentation that WiX was included in the OS with Windows Server 2008, but I can't be sure as I have scoured so much material for an answer that I may have dreamed it :). It isn't anywhere that I can find, however. Can you please help me? I've spent way too long on this and am behind schedule. Thank you, Jeannie -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] HELP ...
It isn't there, is it compatible with Windows Server 2008? Are there any prerequisites? Could I have gotten a bad drop? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, January 07, 2010 11:16 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] HELP ... candle.exe, light.exe etc are installed by default to C:\Program Files\Windows Installer XML v3\bin Wix isnt distributed with any OS. It was going to be in Visual Studio but this never happened so the only distributions are on the sourceforge project page. -Original Message- From: Jeannie Efird [mailto:jeannie.ef...@theaba.org] Sent: 07 January 2010 15:18 To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] HELP ... I am setting up CI utilizing CCNet and MSBuild. I've come to the realization that MSBuild will not work with a Web Deployment Project (vdproj) to create an MSI. Therefore, I am attempting to utilize WiX as the intermediary as I do not want to install Visual Studio on the build box. We are developing in VS 2008 and the OS is Windows Server 2008. However, I cannot seem to get Wix installed in this environment. The Windows Installer XML toolset appears in the program files but doesn't work as WiX doesn't appear to be available. I have searched for each of the executables, to no avail. I think I read some documentation that WiX was included in the OS with Windows Server 2008, but I can't be sure as I have scoured so much material for an answer that I may have dreamed it :). It isn't anywhere that I can find, however. Can you please help me? I've spent way too long on this and am behind schedule. Thank you, Jeannie -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question about Shared Components and their Key Paths
1. Good. This is really the only correct solution. 2. The Windows Installer manages the folder the Component is installed to for each Product. Thus, changing the installation folder works fine. The KeyPath is just the File or RegistryKey or ODBC Driver (does anybody use this anymore?). Note: you can get things confused if you put a Property reference in the middle of your RegistryKey/@Key. In your example below, the KeyPath for the Components is the same if it is always SharedDll. Note: the Windows Installer's special handling of the folder makes it tricky to state the Component Rules. I saw someone regularly stating a simplified version of the Component Rules on Stack Overflow that could lead to confusion like yours. I kept trying to correct the statements as I found them. smile/ 3. Uninstall is hosed as well. This just does not work. Check out this old blog post about Component Rules and hopefully it helps: http://robmensching.com/blog/posts/2003/10/18/Component-Rules-101 On Thu, Jan 7, 2010 at 1:58 AM, Ondrej Zarevucky ondrej.zarevu...@fine.czwrote: Hi everybody, we have more products sharing the same shared libraries and I'd like to clarify some things, before I proceed. 1) Shared component between two products using same KeyPath and same Guid. - From earlier discussion I understand this is the proper solution and in my tests everything works perfectly. 2) Shared component between two products using DIFFERENT KeyPaths, but SAME Guid. - I've read http://blogs.msdn.com/heaths/archive/2009/12/21/about-shared-components.aspx , but I don't understand if it is supported solution or just one which works, because it needs to work for compatibility reasons. - How should I solve this issue, if the MSIs are authored to use same KeyPaths, but the user is allowed to change the Target Directory independently for each install? Example: - ProductOne and ProductTwo both use SharedLib.Dll with same Guid; - ProductOne installs the SharedLib.Dll in FolderOne - ProductTwo installs the SharedLib.Dll in FolderTwo 3) Shared component between two products using SAME KeyPaths, but DIFFERENT Guids. - I understand the library would get overwritten using the versioning rules. Will this properly work for uninstalls? I need both products to work when the other gets uninstalled. BTW: For updates we are using Major Upgrades. Thank you for clarification. Ondřej Zarevúcky -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] HELP ...
I still don't understand. Did you install the WiX3.msi (which installs the binaries and MSBuild targets files correctly)? The WiX toolset is not built into the operating system but is compatible with everything from Windows XP and up. On Thu, Jan 7, 2010 at 8:19 AM, Jeannie Efird jeannie.ef...@theaba.orgwrote: It isn't there, is it compatible with Windows Server 2008? Are there any prerequisites? Could I have gotten a bad drop? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, January 07, 2010 11:16 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] HELP ... candle.exe, light.exe etc are installed by default to C:\Program Files\Windows Installer XML v3\bin Wix isnt distributed with any OS. It was going to be in Visual Studio but this never happened so the only distributions are on the sourceforge project page. -Original Message- From: Jeannie Efird [mailto:jeannie.ef...@theaba.org] Sent: 07 January 2010 15:18 To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] HELP ... I am setting up CI utilizing CCNet and MSBuild. I've come to the realization that MSBuild will not work with a Web Deployment Project (vdproj) to create an MSI. Therefore, I am attempting to utilize WiX as the intermediary as I do not want to install Visual Studio on the build box. We are developing in VS 2008 and the OS is Windows Server 2008. However, I cannot seem to get Wix installed in this environment. The Windows Installer XML toolset appears in the program files but doesn't work as WiX doesn't appear to be available. I have searched for each of the executables, to no avail. I think I read some documentation that WiX was included in the OS with Windows Server 2008, but I can't be sure as I have scoured so much material for an answer that I may have dreamed it :). It isn't anywhere that I can find, however. Can you please help me? I've spent way too long on this and am behind schedule. Thank you, Jeannie -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Build WiX Solution After Drop
You'll have to edit the wix.targets file to build after the AfterDrop target or run your .wixproj after the other things build. Or, do your SQL Database manipulation earlier in the build process. On Thu, Jan 7, 2010 at 7:57 AM, Kerber, Cameron cameron.ker...@philips.comwrote: So I created a Wix Solution and added it to my Team Build process as the last solution to build. But I am using source files inside WiX that aren't created until after my solutions have built and deployed... So how do I delay the WiX compile. Specifically my problem is on the AfterDrop target I am deploying SQL Databases that create sql scripts on the fly. I need those scripts to be wrapped into Wix. But the AfterDrop target is called long after my WiX solution built. THanks! The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] HELP ...
I'm going to do a clean drop. To ensure that this is accurate, can you provide the url that DOES NOT have the Votive UI that requires VS, as that is not going to be loaded on the build box? -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, January 07, 2010 11:16 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] HELP ... What are the exact failures you are seeing? If it is an install failure, can you send along the verbose log file? On Thu, Jan 7, 2010 at 7:17 AM, Jeannie Efird jeannie.ef...@theaba.orgwrote: I am setting up CI utilizing CCNet and MSBuild. I've come to the realization that MSBuild will not work with a Web Deployment Project (vdproj) to create an MSI. Therefore, I am attempting to utilize WiX as the intermediary as I do not want to install Visual Studio on the build box. We are developing in VS 2008 and the OS is Windows Server 2008. However, I cannot seem to get Wix installed in this environment. The Windows Installer XML toolset appears in the program files but doesn't work as WiX doesn't appear to be available. I have searched for each of the executables, to no avail. I think I read some documentation that WiX was included in the OS with Windows Server 2008, but I can't be sure as I have scoured so much material for an answer that I may have dreamed it :). It isn't anywhere that I can find, however. Can you please help me? I've spent way too long on this and am behind schedule. Thank you, Jeannie -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] HELP ...
It should be self-contained. This is the download link. I would suggest uninstalling the toolset, downloading this and reinstalling, just to be sure. http://sourceforge.net/projects/wix/files/WiX%20v3.0%20%28stable%29/3.0. 5419.0%20RTM/wix3.0.5419.0-x86-setup.zip/download If that doesnt fix it, Im not sure what the trouble might be, although Im on XP, not 2008. -Original Message- From: Jeannie Efird [mailto:jeannie.ef...@theaba.org] Sent: 07 January 2010 16:19 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] HELP ... It isn't there, is it compatible with Windows Server 2008? Are there any prerequisites? Could I have gotten a bad drop? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, January 07, 2010 11:16 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] HELP ... candle.exe, light.exe etc are installed by default to C:\Program Files\Windows Installer XML v3\bin Wix isnt distributed with any OS. It was going to be in Visual Studio but this never happened so the only distributions are on the sourceforge project page. -Original Message- From: Jeannie Efird [mailto:jeannie.ef...@theaba.org] Sent: 07 January 2010 15:18 To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] HELP ... I am setting up CI utilizing CCNet and MSBuild. I've come to the realization that MSBuild will not work with a Web Deployment Project (vdproj) to create an MSI. Therefore, I am attempting to utilize WiX as the intermediary as I do not want to install Visual Studio on the build box. We are developing in VS 2008 and the OS is Windows Server 2008. However, I cannot seem to get Wix installed in this environment. The Windows Installer XML toolset appears in the program files but doesn't work as WiX doesn't appear to be available. I have searched for each of the executables, to no avail. I think I read some documentation that WiX was included in the OS with Windows Server 2008, but I can't be sure as I have scoured so much material for an answer that I may have dreamed it :). It isn't anywhere that I can find, however. Can you please help me? I've spent way too long on this and am behind schedule. Thank you, Jeannie -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] HELP ...
Server 2008 is x64 only (unless you're using an Itanium system which is rather unlikely). Try looking in C:\Program Files (x86)\Windows Installer XML v3\bin\ Does WiX show up in the ARP list? Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** 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: Jeannie Efird [mailto:jeannie.ef...@theaba.org] Sent: 07 January 2010 16:19 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] HELP ... It isn't there, is it compatible with Windows Server 2008? Are there any prerequisites? Could I have gotten a bad drop? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, January 07, 2010 11:16 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] HELP ... candle.exe, light.exe etc are installed by default to C:\Program Files\Windows Installer XML v3\bin Wix isnt distributed with any OS. It was going to be in Visual Studio but this never happened so the only distributions are on the sourceforge project page. -Original Message- From: Jeannie Efird [mailto:jeannie.ef...@theaba.org] Sent: 07 January 2010 15:18 To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] HELP ... I am setting up CI utilizing CCNet and MSBuild. I've come to the realization that MSBuild will not work with a Web Deployment Project (vdproj) to create an MSI. Therefore, I am attempting to utilize WiX as the intermediary as I do not want to install Visual Studio on the build box. We are developing in VS 2008 and the OS is Windows Server 2008. However, I cannot seem to get Wix installed in this environment. The Windows Installer XML toolset appears in the program files but doesn't work as WiX doesn't appear to be available. I have searched for each of the executables, to no avail. I think I read some documentation that WiX was included in the OS with Windows Server 2008, but I can't be sure as I have scoured so much material for an answer that I may have dreamed it :). It isn't anywhere that I can find, however. Can you please help me? I've spent way too long on this and am behind schedule. Thank you, Jeannie -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___
Re: [WiX-users] HELP ...
I did a clean drop, at the url below. The first message is that is a prerequisite dialog box stating that the Votive toolkit couldn't be installed because VS 2005 / 2008 is not located on the machine. (By design). I just reinstalled and they have appeared in the designated folder, go figure. Must've been a bad drop. Sorry. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, January 07, 2010 11:34 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] HELP ... It should be self-contained. This is the download link. I would suggest uninstalling the toolset, downloading this and reinstalling, just to be sure. http://sourceforge.net/projects/wix/files/WiX%20v3.0%20%28stable%29/3.0. 5419.0%20RTM/wix3.0.5419.0-x86-setup.zip/download If that doesnt fix it, Im not sure what the trouble might be, although Im on XP, not 2008. -Original Message- From: Jeannie Efird [mailto:jeannie.ef...@theaba.org] Sent: 07 January 2010 16:19 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] HELP ... It isn't there, is it compatible with Windows Server 2008? Are there any prerequisites? Could I have gotten a bad drop? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, January 07, 2010 11:16 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] HELP ... candle.exe, light.exe etc are installed by default to C:\Program Files\Windows Installer XML v3\bin Wix isnt distributed with any OS. It was going to be in Visual Studio but this never happened so the only distributions are on the sourceforge project page. -Original Message- From: Jeannie Efird [mailto:jeannie.ef...@theaba.org] Sent: 07 January 2010 15:18 To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] HELP ... I am setting up CI utilizing CCNet and MSBuild. I've come to the realization that MSBuild will not work with a Web Deployment Project (vdproj) to create an MSI. Therefore, I am attempting to utilize WiX as the intermediary as I do not want to install Visual Studio on the build box. We are developing in VS 2008 and the OS is Windows Server 2008. However, I cannot seem to get Wix installed in this environment. The Windows Installer XML toolset appears in the program files but doesn't work as WiX doesn't appear to be available. I have searched for each of the executables, to no avail. I think I read some documentation that WiX was included in the OS with Windows Server 2008, but I can't be sure as I have scoured so much material for an answer that I may have dreamed it :). It isn't anywhere that I can find, however. Can you please help me? I've spent way too long on this and am behind schedule. Thank you, Jeannie -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net
Re: [WiX-users] HELP ...
It didn't: I did yet another clean drop. The first message is that is a prerequisite dialog box stating that the Votive toolkit couldn't be installed because VS 2005 / 2008 is not located on the machine. (By design). I just reinstalled and they have appeared in the designated folder, go figure. Must've been a bad drop. Sorry. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Thursday, January 07, 2010 11:26 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] HELP ... Server 2008 is x64 only (unless you're using an Itanium system which is rather unlikely). Try looking in C:\Program Files (x86)\Windows Installer XML v3\bin\ Does WiX show up in the ARP list? Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** 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: Jeannie Efird [mailto:jeannie.ef...@theaba.org] Sent: 07 January 2010 16:19 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] HELP ... It isn't there, is it compatible with Windows Server 2008? Are there any prerequisites? Could I have gotten a bad drop? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, January 07, 2010 11:16 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] HELP ... candle.exe, light.exe etc are installed by default to C:\Program Files\Windows Installer XML v3\bin Wix isnt distributed with any OS. It was going to be in Visual Studio but this never happened so the only distributions are on the sourceforge project page. -Original Message- From: Jeannie Efird [mailto:jeannie.ef...@theaba.org] Sent: 07 January 2010 15:18 To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] HELP ... I am setting up CI utilizing CCNet and MSBuild. I've come to the realization that MSBuild will not work with a Web Deployment Project (vdproj) to create an MSI. Therefore, I am attempting to utilize WiX as the intermediary as I do not want to install Visual Studio on the build box. We are developing in VS 2008 and the OS is Windows Server 2008. However, I cannot seem to get Wix installed in this environment. The Windows Installer XML toolset appears in the program files but doesn't work as WiX doesn't appear to be available. I have searched for each of the executables, to no avail. I think I read some documentation that WiX was included in the OS with Windows Server 2008, but I can't be sure as I have scoured so much material for an answer that I may have dreamed it :). It isn't anywhere that I can find, however. Can you please help me? I've spent way too long on this and am behind schedule. Thank you, Jeannie -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
Re: [WiX-users] HELP ...
I did yet another clean drop. The first message is that is a prerequisite dialog box stating that the Votive toolkit couldn't be installed because VS 2005 / 2008 is not located on the machine. (By design). I just reinstalled and they have appeared in the designated folder, go figure. Must've been a bad drop. Sorry. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, January 07, 2010 11:29 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] HELP ... I still don't understand. Did you install the WiX3.msi (which installs the binaries and MSBuild targets files correctly)? The WiX toolset is not built into the operating system but is compatible with everything from Windows XP and up. On Thu, Jan 7, 2010 at 8:19 AM, Jeannie Efird jeannie.ef...@theaba.orgwrote: It isn't there, is it compatible with Windows Server 2008? Are there any prerequisites? Could I have gotten a bad drop? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, January 07, 2010 11:16 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] HELP ... candle.exe, light.exe etc are installed by default to C:\Program Files\Windows Installer XML v3\bin Wix isnt distributed with any OS. It was going to be in Visual Studio but this never happened so the only distributions are on the sourceforge project page. -Original Message- From: Jeannie Efird [mailto:jeannie.ef...@theaba.org] Sent: 07 January 2010 15:18 To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] HELP ... I am setting up CI utilizing CCNet and MSBuild. I've come to the realization that MSBuild will not work with a Web Deployment Project (vdproj) to create an MSI. Therefore, I am attempting to utilize WiX as the intermediary as I do not want to install Visual Studio on the build box. We are developing in VS 2008 and the OS is Windows Server 2008. However, I cannot seem to get Wix installed in this environment. The Windows Installer XML toolset appears in the program files but doesn't work as WiX doesn't appear to be available. I have searched for each of the executables, to no avail. I think I read some documentation that WiX was included in the OS with Windows Server 2008, but I can't be sure as I have scoured so much material for an answer that I may have dreamed it :). It isn't anywhere that I can find, however. Can you please help me? I've spent way too long on this and am behind schedule. Thank you, Jeannie -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined,
Re: [WiX-users] HELP ...
Well if it didn't show up in the ARP list didn't show up in the directory I pasted below then you didn't install it since it sounds like you never uninstalled it before reinstalling it just confirms that. Also pasting the same text into 3 replies isn't necessary. We can read it the first time thanks. Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** 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: Jeannie Efird [mailto:jeannie.ef...@theaba.org] Sent: 07 January 2010 16:43 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] HELP ... It didn't: I did yet another clean drop. The first message is that is a prerequisite dialog box stating that the Votive toolkit couldn't be installed because VS 2005 / 2008 is not located on the machine. (By design). I just reinstalled and they have appeared in the designated folder, go figure. Must've been a bad drop. Sorry. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Thursday, January 07, 2010 11:26 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] HELP ... Server 2008 is x64 only (unless you're using an Itanium system which is rather unlikely). Try looking in C:\Program Files (x86)\Windows Installer XML v3\bin\ Does WiX show up in the ARP list? Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** 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: Jeannie Efird [mailto:jeannie.ef...@theaba.org] Sent: 07 January 2010 16:19 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] HELP ... It isn't there, is it compatible with Windows Server 2008? Are there any prerequisites? Could I have gotten a bad drop? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, January 07, 2010 11:16 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] HELP ... candle.exe, light.exe etc are installed by default to C:\Program Files\Windows Installer XML v3\bin Wix isnt distributed with any OS. It was going to be in Visual Studio but this never happened so the only distributions are on the sourceforge project page. -Original Message- From: Jeannie Efird [mailto:jeannie.ef...@theaba.org] Sent: 07 January 2010 15:18 To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] HELP ... I am setting up CI utilizing CCNet and MSBuild. I've come to the realization that MSBuild will not work with a Web Deployment Project (vdproj) to create an MSI. Therefore, I am attempting to utilize WiX as the intermediary as I do not want to install Visual Studio on the build box. We are developing in VS 2008 and the OS is Windows Server 2008. However, I cannot seem to get Wix installed in this environment. The Windows Installer XML toolset appears in the program files but doesn't work as WiX doesn't appear to be available. I have searched for each of the executables, to no avail. I think I read some documentation that WiX was included in the OS with Windows Server 2008, but I can't be sure as I have scoured so much material for an answer that I may have dreamed it :). It isn't anywhere that I can find, however. Can you please help me? I've spent way too long on this and am behind schedule. Thank you, Jeannie -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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. -- This SF.Net email is sponsored
[WiX-users] Added ErrorLog Dialog at end of Install...
Hi All, What would be the best way to add a custom ErrorLog Dialog that is only displayed if an error occurs during installation and it would appear right at the end of the installation in that case. The idea is that this ErrorDialog would contain the install log and there would be a button to email the log to us at the press of a button or 2. Any ideas Thanks, DOMINIQUE LOUIS | IS DEVELOPER, AMX DIGITAL MEDIA GROUP dominique.lo...@amxeurope.com AMX AMX UK Auster Road Clifton Moor York, North Yorkshire United Kingdom YO30 4GD +44 (0) 1904 343100 office +44 (0) 1904 343101 fax AMX South 6th Floor Salisbury House London Wall London United Kingdom EC2M 5QQ +44 (0) 2076 529450 office +44 (0) 8701 991661 fax AMX Belgium Boerenkrijglaan, 96a B-2260 Westerlo Belgium + 32 (0) 1454 2763 office + 32 (0) 1454 2766 fax ## Attention: This e-mail message is privileged and confidential. If you are not the intended recipient please delete the message and notify the sender. Any views or opinions presented are solely those of the author. This email was scanned and cleared by NetIQ MailMarshal. ## -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Silly question: what is my user name (it doesn't appear to be my email)
Sorry for what amounts to account management spam, but the emails I received when I signed up gave me my password, but nowhere does it say what my user ID is. I assumed it must be my email address, but the login form only lets me type 15 characters. My email stripping off the domain doesn't work either. How does one find out what username was assigned to them in the initial registration process? (I did my registration entirely via the email mechanism). -- Bryan Reich -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix bug when converting class/progID set from advertised=yes to advertised=no?
Bug 2927773 has been opened to track. Thanks.
-Original Message-
From: Bryan Reich [mailto:bryan.re...@microsoft.com]
Sent: Wednesday, January 06, 2010 10:12 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wix bug when converting class/progID set from
advertised=yes to advertised=no?
New member to the community. How do I file a bug?
--
Bryan
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, January 06, 2010 9:35 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Wix bug when converting class/progID set from
advertised=yes to advertised=no?
Yeah, this is a bug in WiX v3.0 and WiX v3.5. This is the busted logic:
if (null != parent) // if this is a version
independent ProgId
{
if (YesNoType.Yes == firstProgIdForClass)
{
this.core.CreateRegistryRow(sourceLineNumbers,
MsiInterop.MsidbRegistryRootClassesRoot, String.Concat(CLSID\\, classId,
\\VersionIndependentProgID), String.Empty, progId, componentId);
}
this.core.CreateRegistryRow(sourceLineNumbers,
MsiInterop.MsidbRegistryRootClassesRoot, String.Concat(progId, \\CurVer),
String.Empty, parent, componentId);
}
else
{
if (null == parent)
{
this.core.CreateRegistryRow(sourceLineNumbers,
MsiInterop.MsidbRegistryRootClassesRoot, String.Concat(CLSID\\, classId,
\\ProgID), String.Empty, progId, componentId);
}
}
I think that second check for null == parent should have been YesNoType.Yes
== firstProgIdForClass.
Do you mind filing a bug?
The work around in WiX v3.0, unfortunately, is to pull the second ProgId out
and set its registry keys using RegistryKey/RegistryValue elements.
On Wed, Jan 6, 2010 at 8:37 PM, Bryan Reich bryan.re...@microsoft.comwrote:
I can confirm that not only does nesting the progIDs not solve the
issue, it actually produces a build failure.
Firstly, it appears the wix documentation's claims that nesting of
more than a single ProgId under another progID creates COM aliases is
incorrect (or perhaps doesn't apply to advertise=no nodes) because
it tries to treat all of them like version independent ProgId entries and
fails to compile.
(Error message: Version independent ProgIds cannot have Icons. Remove
the Icon and/or IconIndex attributes from your ProgId element)
Second, it says that ProgId elements can only be nested up to a single
level deep (i.e. only ProgId Id=Prog1
ProgId Id=VerIndepProg /
/ProgId
And not
ProgId Id=Prog1
ProgId Id=VerIndepProg /
ProgId Id=OtherProg2
ProgId Id=VerIndepOtherProg /
/ProgId
/ProgId
)
(error message: ProgId elements may not be nested more than 1 level
deep.)
And unfortunately I need to do the latter because a number of the
same-class associated progIds also have versions and
version-independent entries.
--
Bryan
-Original Message-
From: Bryan Reich
Sent: Wednesday, January 06, 2010 7:41 PM
To: 'Bob Arnson'; General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] Wix bug when converting class/progID set from
advertised=yes to advertised=no?
I was looking into that very question, but I don't think it yields the
same affect.
For one thing, when you nest a progID thusly:
ProgId Id=MyProgId.12
ProgId Id=MyProgId /
/ProgId
This indicates that MyProgId is the version independent ProgId for
MyProgId.12. The wix documentation for the ProgId Element:
...
Chidren
Sequence (min: 1, max:1)
1. ProgId (min: 0, max: unbounded): The version-independent ProgId
must be the first child elment of the actual ProgId. Nesting other
ProgId elements within the Version-independent ProgId will create COM+
aliases, see
http://support.microsoft.com/kb/305745 for more information.
So the first point I should make is that I'm not sure that every
ProgId in question has a version-independent ProgId to associate with
it, in which case would mean I have nothing to nest as the first
element. Second, the successive ProgIds are COM+ aliases, and while
the documentation on these is terrible as far as I've been able to
hunt down, it appears they don't serve quite the same purpose as what
I am alluding to above. COM+ aliases not only generate an alternate
ProgID, but also an alternate Class ID associated with that ProgId
that happens I believe to point to the same server object. That being
said, not being familiar with COM+ aliases well at all, I could be off
base here, and I'm not fully sure how this operates in the installer,
so that might give me something like what I would want, providing the
first pesky
Re: [WiX-users] Build WiX Solution After Drop
You'll have to do some pretty major MSBuild/TeamBuild hacks to perform the database deployment before the wix solution is built. Are you using VSTS DB project files to maintain your database schema? Are you using it's deployment feature to generate the *.sql? If so, are you deploying the database onto a clean environment? If yes, have you considered generating the *.sql file only (without deployment)? In that case, you might be able to perform the generation as a AfterBuild step in the *.dbproj project itself. If you need to compare against a live database, then I suggest you package up the XML schema and accompanying files in the wix package itself and use vsdbcmd.exe to generate and deploy at install-time or right after installation. There's no built-in help to do any of these things though... Another solution might be to split up the build process (that's got its own problems... like where to do you get the build output?)... Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Kerber, Cameron [mailto:cameron.ker...@philips.com] Sent: Thursday, January 07, 2010 7:57 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Build WiX Solution After Drop So I created a Wix Solution and added it to my Team Build process as the last solution to build. But I am using source files inside WiX that aren't created until after my solutions have built and deployed... So how do I delay the WiX compile. Specifically my problem is on the AfterDrop target I am deploying SQL Databases that create sql scripts on the fly. I need those scripts to be wrapped into Wix. But the AfterDrop target is called long after my WiX solution built. THanks! The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. --- --- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Build WiX Solution After Drop
Does anyone have any pointers towards using a setup.ini file for setting parameters of an install? -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, January 07, 2010 1:52 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Build WiX Solution After Drop You'll have to do some pretty major MSBuild/TeamBuild hacks to perform the database deployment before the wix solution is built. Are you using VSTS DB project files to maintain your database schema? Are you using it's deployment feature to generate the *.sql? If so, are you deploying the database onto a clean environment? If yes, have you considered generating the *.sql file only (without deployment)? In that case, you might be able to perform the generation as a AfterBuild step in the *.dbproj project itself. If you need to compare against a live database, then I suggest you package up the XML schema and accompanying files in the wix package itself and use vsdbcmd.exe to generate and deploy at install-time or right after installation. There's no built-in help to do any of these things though... Another solution might be to split up the build process (that's got its own problems... like where to do you get the build output?)... Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Kerber, Cameron [mailto:cameron.ker...@philips.com] Sent: Thursday, January 07, 2010 7:57 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Build WiX Solution After Drop So I created a Wix Solution and added it to my Team Build process as the last solution to build. But I am using source files inside WiX that aren't created until after my solutions have built and deployed... So how do I delay the WiX compile. Specifically my problem is on the AfterDrop target I am deploying SQL Databases that create sql scripts on the fly. I need those scripts to be wrapped into Wix. But the AfterDrop target is called long after my WiX solution built. THanks! The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. --- --- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Build WiX Solution After Drop
(Apologize for the previous off-topic email) We actually did something similar to this using a 2nd build script. The first build script build everything EXCEPT the installers, and then as the last step of the build script, we executed the second build script to create the installers themselves. -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Thursday, January 07, 2010 1:52 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Build WiX Solution After Drop You'll have to do some pretty major MSBuild/TeamBuild hacks to perform the database deployment before the wix solution is built. Are you using VSTS DB project files to maintain your database schema? Are you using it's deployment feature to generate the *.sql? If so, are you deploying the database onto a clean environment? If yes, have you considered generating the *.sql file only (without deployment)? In that case, you might be able to perform the generation as a AfterBuild step in the *.dbproj project itself. If you need to compare against a live database, then I suggest you package up the XML schema and accompanying files in the wix package itself and use vsdbcmd.exe to generate and deploy at install-time or right after installation. There's no built-in help to do any of these things though... Another solution might be to split up the build process (that's got its own problems... like where to do you get the build output?)... Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail -Original Message- From: Kerber, Cameron [mailto:cameron.ker...@philips.com] Sent: Thursday, January 07, 2010 7:57 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Build WiX Solution After Drop So I created a Wix Solution and added it to my Team Build process as the last solution to build. But I am using source files inside WiX that aren't created until after my solutions have built and deployed... So how do I delay the WiX compile. Specifically my problem is on the AfterDrop target I am deploying SQL Databases that create sql scripts on the fly. I need those scripts to be wrapped into Wix. But the AfterDrop target is called long after my WiX solution built. THanks! The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. --- --- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Disable repair and admin setup...
Is there some way we can disable (abort install action) if someone were to launch our msi with the /a (administrative install) or /f (repair) options? We can hide the actions in the UI, but when launched via command-line they can still occur, we'd like to disable them for now. -- Tony -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] unexplained Custom Action failure
I setup a Custom Action to call a simple command line utility I created that installs an SSL certificate. It keeps failing so I took the contents of the log file that have the Custom Action arguments and execute them manually in a command window. Of course, the certificate installs correctly. I even changed the account running the MSI to run as me so I could eliminate any security/credentials issues and I get the same result; it fails when running from the MSI and succeeds when running as me. I then loaded up SysInternals procmon to compare the execution of this command line utility in each scenario. All of the procmon parameters are identical!! This includes command line args, user account executing the process and bitness of the process. Note that the installer is running on Windows Server 2008 VM server and in each case the command line is running a 64 bit process. Here are the .wxs snippets for the custom action, and the resulting command line: CustomAction Id=Set_InstallDITDaoSslCertificateArgs Property=InstallDITDaoSslCertificateArgs Value=/ce:add /cf:quot;[UTILITYPATH]UsSslCert.pfxquot; /cpwd:[SSLCERTPWD] /cs:my /cl:localmachine /cid:quot;[SSLCERTID]quot; Execute=immediate / CustomAction Id=InstallDITDaoSslCertificateToPersonal Directory=UTILITYPATH ExeCommand=quot;[UTILITYPATH]InstallUtil.exequot; [InstallDITDaoSslCertificateArgs] Execute=immediate Return=ignore / c:\RevProxy\Install\DAO\InstallUtil\InstallUtil.exe /ce:add /cf:c:\RevProxy\Install\DAO\InstallUtil\UsSslCert.pfx /cpwd:ABB66C32-D9F9-6c9a-81C7-C998FF444C32 /cs:my /cl:localmachine /cid: AbzJc2FFmQeHJGAZrgU9bAjMGbX= Of course, I have changed the sensitive data to protect the innocent... Any idea why this could be failing inside the MSI? I am pulling my hair out at this point. Thanks. - Phil -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] unexplained Custom Action failure
Have you considered using the iis:Certificate (and related) elements instead of your own custom action? These will likely have fewer bugs (lower chance of setup failure) than a custom-coded solution, as well as handle repair, uninstall, patching, etc. correctly. Part of the philosophy underlying wix's design is that users should only write declarative authoring to represent the things they want installed, and let the installation engine (and/or the built-in wix custom actions) handle the actual installation for you. Thanks, Mike Carlson -Original Message- From: phillip_sid...@dellteam.com [mailto:phillip_sid...@dellteam.com] Sent: Thursday, January 07, 2010 1:10 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] unexplained Custom Action failure I setup a Custom Action to call a simple command line utility I created that installs an SSL certificate. It keeps failing so I took the contents of the log file that have the Custom Action arguments and execute them manually in a command window. Of course, the certificate installs correctly. I even changed the account running the MSI to run as me so I could eliminate any security/credentials issues and I get the same result; it fails when running from the MSI and succeeds when running as me. I then loaded up SysInternals procmon to compare the execution of this command line utility in each scenario. All of the procmon parameters are identical!! This includes command line args, user account executing the process and bitness of the process. Note that the installer is running on Windows Server 2008 VM server and in each case the command line is running a 64 bit process. Here are the .wxs snippets for the custom action, and the resulting command line: CustomAction Id=Set_InstallDITDaoSslCertificateArgs Property=InstallDITDaoSslCertificateArgs Value=/ce:add /cf:quot;[UTILITYPATH]UsSslCert.pfxquot; /cpwd:[SSLCERTPWD] /cs:my /cl:localmachine /cid:quot;[SSLCERTID]quot; Execute=immediate / CustomAction Id=InstallDITDaoSslCertificateToPersonal Directory=UTILITYPATH ExeCommand=quot;[UTILITYPATH]InstallUtil.exequot; [InstallDITDaoSslCertificateArgs] Execute=immediate Return=ignore / c:\RevProxy\Install\DAO\InstallUtil\InstallUtil.exe /ce:add /cf:c:\RevProxy\Install\DAO\InstallUtil\UsSslCert.pfx /cpwd:ABB66C32-D9F9-6c9a-81C7-C998FF444C32 /cs:my /cl:localmachine /cid: AbzJc2FFmQeHJGAZrgU9bAjMGbX= Of course, I have changed the sensitive data to protect the innocent... Any idea why this could be failing inside the MSI? I am pulling my hair out at this point. Thanks. - Phil -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Disable repair and admin setup...
I'm not too familiar with Administrative installs, but I would assume you could condition something in the AdminExecuteSequence and AdminUISequence to abort the install. Aborting if a repair is triggered sounds like a very strange request, what if your KeyPaths are damaged and you have advertised shortcuts? Windows Installer can no longer repair them and your app would likely fail to launch. The 'repair' functionality of Windows Installer is part of why you would choose to use MSI in the first place. If you're trying to bypass the resiliency features then maybe a non-MSI setup would be a better choice. Sascha On Fri, Jan 8, 2010 at 7:38 AM, Tony yellowjacketl...@gmail.com wrote: Is there some way we can disable (abort install action) if someone were to launch our msi with the /a (administrative install) or /f (repair) options? We can hide the actions in the UI, but when launched via command-line they can still occur, we'd like to disable them for now. -- Tony -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Disable repair and admin setup...
We did this in one case by using a Condition as follows: Condition Message=your error messageACTION~lt;gt;ADMIN/Condition I know that works for advertise. I think there can be similar logic for repair. -- Bryan -Original Message- From: Tony [mailto:yellowjacketl...@gmail.com] Sent: Thursday, January 07, 2010 12:38 PM To: WiX Users Subject: [WiX-users] Disable repair and admin setup... Is there some way we can disable (abort install action) if someone were to launch our msi with the /a (administrative install) or /f (repair) options? We can hide the actions in the UI, but when launched via command-line they can still occur, we'd like to disable them for now. -- Tony -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Passing installation parameter to exe
The second questions asks if you can set registry values/write file changes/whatever else that running the preagent.exe would have done for you to avoid using it. Is preagent.exe needed by your installation after it is complete or only when installing, repairing, upgrading, and possibly removing the product? -Original Message- From: Shlomi Tsadok [mailto:shl...@tsadok.net] Sent: Wednesday, January 06, 2010 10:44 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Passing installation parameter to exe 1. Preagent.exe is an instalation file of Novell ZenWorks agent. 2. I need to call it with parameters as the installing user(the system account in this case). 3. It will run unatennded, enforced by a machine GPO. 4. It should have those parameters every time it runs. Can you do the same thing to the OS that it does with those parameters without running it? Sorry, I didn't understand this quastion.. Thanks for your time, Shlomi On Wed, Jan 6, 2010 at 6:26 PM, Blair os...@live.com wrote: Preagent.exe is a file you are installing, using for configuration, or both? You need to call it with those parameters as the installing user or elevated? It needs to be visible to the user when it runs or not? It should have those parameters every time it runs or just once? Can you do the same thing to the OS that it does with those parameters without running it? -Original Message- From: Shlomi Tsadok [mailto:shl...@tsadok.net] Sent: Wednesday, January 06, 2010 7:23 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Passing installation parameter to exe Hi, Here is the relevant lines from the wxs file: Component Id=zenpreagent Guid=CB70B54B-9BD2-4cc5-8D80-E129A7C02192 File Id=zenpreagent LongName=preagent.exe Name=PREAGENT.EXE src=\\mf1\apps\Users\APPS_XP\Zen10Agent\GPO_MSI\preagent.exe DiskId=1 Compressed=no/ /Component How do I pass installtion parameters to preagent.exe? For example preagent.exe -d d:\tmp Thanks, Shlomi -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Update imported registry entries
From what few details you provide I assume your CA is an immediate CA that adds temporary rows to the Registry table. Is that correct? -Original Message- From: Andy2k8 [mailto:appr...@gmail.com] Sent: Wednesday, January 06, 2010 10:44 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Update imported registry entries I use a custom action during an upgrade to export and import the existing registry entries. Previous registry setting are getting imported successfully but now i need to change hive version from 1.0 to 2.0 and add few extra keys that is part of the 2.0 version. I have tried sequencing the CA before WriteRegistryValues, but no luck any ideas?? - Andy MSI Developer Schneider Electric:working: -- View this message in context: http://n2.nabble.com/Update-imported-registry-entries-tp4265121p4265121.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Disable repair and admin setup...
Well not really. An admin install isn't anything to do with the actual running installed product, it just extracts the files out, which is probably what you want to prevent (why?). If you think you've concealed your files by preventing an admin install, good luck with that! Also, beware that an administrative install is used during the process of creating a patch, so if you plan to ship patches don't shoot yourself in the foot there. A repair is an attempt to correct the installed product where something is by definition broken, and that's very different from the idea of an admin install. If you don't let repair proceed the product will remain broken, and not only might it keep trying to repair indefinitely, you may also find that upgrades and patches won't work if the files installed don't match what the MSI file thinks should be there. Every time I find someone trying to prevent repair it's because they want to do something like remove some files (or registry entries) after the install. If that's the case, there is a way to do that (a null ComponentID). Or if the repair is executing some custom action again, then the problem is that the condition on the custom action is incomplete. What is the problem that you believe disabling repair will solve? Phil Wilson -Original Message- From: Bryan Reich [mailto:bryan.re...@microsoft.com] Sent: Thursday, January 07, 2010 1:50 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Disable repair and admin setup... We did this in one case by using a Condition as follows: Condition Message=your error messageACTION~lt;gt;ADMIN/Condition I know that works for advertise. I think there can be similar logic for repair. -- Bryan -Original Message- From: Tony [mailto:yellowjacketl...@gmail.com] Sent: Thursday, January 07, 2010 12:38 PM To: WiX Users Subject: [WiX-users] Disable repair and admin setup... Is there some way we can disable (abort install action) if someone were to launch our msi with the /a (administrative install) or /f (repair) options? We can hide the actions in the UI, but when launched via command-line they can still occur, we'd like to disable them for now. -- Tony -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-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 Portland House, Bressenden Place, London, SW1E 5BF (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77nav_id=80prev_id=77. You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail inet.hqhelpd...@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). -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing
Re: [WiX-users] Silly question: what is my user name (it doesn't appear to be my email)
No clue (I don't know mine either, and I also initially registered via email). One of the early emails from the automated admin gave me this as an admin portal of sorts: https://lists.sourceforge.net/lists/options/wix-users/Bryan.Reich%40microsof t.com - I took the liberty of changing it from my address to yours. -Original Message- From: Bryan Reich [mailto:bryan.re...@microsoft.com] Sent: Thursday, January 07, 2010 10:59 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Silly question: what is my user name (it doesn't appear to be my email) Sorry for what amounts to account management spam, but the emails I received when I signed up gave me my password, but nowhere does it say what my user ID is. I assumed it must be my email address, but the login form only lets me type 15 characters. My email stripping off the domain doesn't work either. How does one find out what username was assigned to them in the initial registration process? (I did my registration entirely via the email mechanism). -- Bryan Reich -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Disable repair and admin setup...
You could simply drop the AdminExecuteSequence (and AdminUISequence) tables. That would prevent administrative installations. I also echo the question of why. Disabling repair is a bigger why?. If you are referring to the Repair button in the Programs and Features window just add the ARPNOREPAIR property Property Id=ARPNOREPAIR Value=1/ to your Product element. That will still allow triggered repairs based on broken installs as well as patching and non-major upgrades, but I personally prefer to see products that allow Repair from the Programs and Features window. If you have custom actions or other issues that break when repair is run, you should seek to fix those instead of disabling repair. Those issues aren't just repair issues, they are also upgrade issues (and possibly even remove issues) that should never be shipped until you fix them. -Original Message- From: Sascha Beaumont [mailto:sascha.beaum...@gmail.com] Sent: Thursday, January 07, 2010 1:49 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Disable repair and admin setup... I'm not too familiar with Administrative installs, but I would assume you could condition something in the AdminExecuteSequence and AdminUISequence to abort the install. Aborting if a repair is triggered sounds like a very strange request, what if your KeyPaths are damaged and you have advertised shortcuts? Windows Installer can no longer repair them and your app would likely fail to launch. The 'repair' functionality of Windows Installer is part of why you would choose to use MSI in the first place. If you're trying to bypass the resiliency features then maybe a non-MSI setup would be a better choice. Sascha On Fri, Jan 8, 2010 at 7:38 AM, Tony yellowjacketl...@gmail.com wrote: Is there some way we can disable (abort install action) if someone were to launch our msi with the /a (administrative install) or /f (repair) options? We can hide the actions in the UI, but when launched via command-line they can still occur, we'd like to disable them for now. -- Tony -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] getting win32 exception while running the newly added custom ICE
Use the dumpbin.exe utility with the /IMPORTS switch on your release custom action dll to see what files it depends on. Check to see if any of those files are missing from the default path of your target machine. If they are, research to see what would be required to statically link to their libraries such that those dlls are no longer required. -Original Message- From: nagaram.c [mailto:nagara...@symphony.cc] Sent: Tuesday, January 06, 2009 9:59 PM To: 'General discussion for Windows Installer XML toolset.'; 'Blair'; ra...@symphony.cc Subject: RE: [WiX-users] getting win32 exception while running the newly added custom ICE The issue still exists for Release build, however works ok with debug build, below is the error log smoke.exe : error SMOK0217 : Error executing ICE action 'ICE900'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for details and how to solve this problem. The following string format was not expected by the external UI message logger: There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. . smoke.exe : error SMOK0217 : Error executing ICE action 'ICE903'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for details and how to solve this problem. The following string format was not expected by the external UI message logger: There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. . - Nag -Original Message- From: nagaram.c [mailto:nagara...@symphony.cc] Sent: Wednesday, January 06, 2010 11:30 PM To: 'Blair'; 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] getting win32 exception while running the newlyadded custom ICE This works, Thank you - Nag -Original Message- From: Blair [mailto:os...@live.com] Sent: Wednesday, January 06, 2010 10:09 AM To: nagara...@symphony.cc; 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] getting win32 exception while running the newly added custom ICE The default build settings for native C++ code generation is to use the runtime DLLs that come with VS2008 (which are NOT resident by default in any OS). For Custom Action use, that isn't the build setting you want. Open the project properties dialog, navigate to Configuration Properties -- C/C++ -- Code Generation, select Debug in the Configuration drop-down at the top of the dialog, change the Runtime Library setting to Multi-threaded Debug (/MTd), select Release in the Configuration drop-down at the top of the dialog (approving saving the changes in the confirmation dialog), change the Runtime Library setting to Multi-threaded (/MT), then hit Apply and OK. -Original Message- From: nagaram.c [mailto:nagara...@symphony.cc] Sent: Wednesday, January 06, 2010 5:17 AM To: 'Blair'; 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] getting win32 exception while running the newly added custom ICE Hi, With the release DLL I am getting these below errors, I am using VS2008 for creating this C++ DLL, can you please suggest which of the linker setting I have to select in the project properties dialog for to specify Static Runtime Library setting. smoke.exe : error SMOK0217 : Error executing ICE action 'ICE900'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for details and how to solve this problem. The following string format was not expected by the external UI message logger: There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. . smoke.exe : error SMOK0217 : Error executing ICE action 'ICE903'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See http://wix.sourceforge.net/faq.html#Error217 for details and how to solve this problem. The following string format was not expected by the external UI message logger: There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. . Thanks, Nag -Original Message- From: Blair [mailto:os...@live.com] Sent: Wednesday, January 06, 2010 4:54 AM To: nagara...@symphony.cc; 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] getting win32 exception while running the newly added custom ICE Is it at all possible that the new ICE900 test you wrote uses the C++ runtime DLL? In your C++ build settings you need to make sure you link to
Re: [WiX-users] Disable repair and admin setup...
We never patch, so that won't be an issue. Thanks for the suggestion regarding admin installs. In the past we have never really supported repair either. So, we strive to prevent it from being triggered. We always use the ARPNOREPAIR, but the question of automated repair came up and we noticed it is still possible to trigger a repair action via that mechanism. We are trying to prevent repair not abort it as I might have suggested above. On Thu, Jan 7, 2010 at 6:01 PM, Blair os...@live.com wrote: You could simply drop the AdminExecuteSequence (and AdminUISequence) tables. That would prevent administrative installations. I also echo the question of why. Disabling repair is a bigger why?. If you are referring to the Repair button in the Programs and Features window just add the ARPNOREPAIR property Property Id=ARPNOREPAIR Value=1/ to your Product element. That will still allow triggered repairs based on broken installs as well as patching and non-major upgrades, but I personally prefer to see products that allow Repair from the Programs and Features window. If you have custom actions or other issues that break when repair is run, you should seek to fix those instead of disabling repair. Those issues aren't just repair issues, they are also upgrade issues (and possibly even remove issues) that should never be shipped until you fix them. -Original Message- From: Sascha Beaumont [mailto:sascha.beaum...@gmail.com] Sent: Thursday, January 07, 2010 1:49 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Disable repair and admin setup... I'm not too familiar with Administrative installs, but I would assume you could condition something in the AdminExecuteSequence and AdminUISequence to abort the install. Aborting if a repair is triggered sounds like a very strange request, what if your KeyPaths are damaged and you have advertised shortcuts? Windows Installer can no longer repair them and your app would likely fail to launch. The 'repair' functionality of Windows Installer is part of why you would choose to use MSI in the first place. If you're trying to bypass the resiliency features then maybe a non-MSI setup would be a better choice. Sascha On Fri, Jan 8, 2010 at 7:38 AM, Tony yellowjacketl...@gmail.com wrote: Is there some way we can disable (abort install action) if someone were to launch our msi with the /a (administrative install) or /f (repair) options? We can hide the actions in the UI, but when launched via command-line they can still occur, we'd like to disable them for now. -- Tony -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Tony -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Disable repair and admin setup...
Tony, I'm echoing Phil and Blair here.. Phil wrote: What is the problem that you believe disabling repair will solve? Blair wrote: If you have custom actions or other issues that break when repair is run, you should seek to fix those instead of disabling repair You shouldn't have to support repair, if repairing your installation breaks something then you're probably doing something wrong and you should be fixing the underlying issue rather than preventing repair. Custom Actions aside, try to think of your MSI as a description of how the system should look. When the system doesn't match the MSI, a repair is initiated. If you want an xcopy type setup, there are alternatives. Sascha On Fri, Jan 8, 2010 at 10:28 AM, Tony yellowjacketl...@gmail.com wrote: We never patch, so that won't be an issue. Thanks for the suggestion regarding admin installs. In the past we have never really supported repair either. So, we strive to prevent it from being triggered. We always use the ARPNOREPAIR, but the question of automated repair came up and we noticed it is still possible to trigger a repair action via that mechanism. We are trying to prevent repair not abort it as I might have suggested above. On Thu, Jan 7, 2010 at 6:01 PM, Blair os...@live.com wrote: You could simply drop the AdminExecuteSequence (and AdminUISequence) tables. That would prevent administrative installations. I also echo the question of why. Disabling repair is a bigger why?. If you are referring to the Repair button in the Programs and Features window just add the ARPNOREPAIR property Property Id=ARPNOREPAIR Value=1/ to your Product element. That will still allow triggered repairs based on broken installs as well as patching and non-major upgrades, but I personally prefer to see products that allow Repair from the Programs and Features window. If you have custom actions or other issues that break when repair is run, you should seek to fix those instead of disabling repair. Those issues aren't just repair issues, they are also upgrade issues (and possibly even remove issues) that should never be shipped until you fix them. -Original Message- From: Sascha Beaumont [mailto:sascha.beaum...@gmail.com] Sent: Thursday, January 07, 2010 1:49 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Disable repair and admin setup... I'm not too familiar with Administrative installs, but I would assume you could condition something in the AdminExecuteSequence and AdminUISequence to abort the install. Aborting if a repair is triggered sounds like a very strange request, what if your KeyPaths are damaged and you have advertised shortcuts? Windows Installer can no longer repair them and your app would likely fail to launch. The 'repair' functionality of Windows Installer is part of why you would choose to use MSI in the first place. If you're trying to bypass the resiliency features then maybe a non-MSI setup would be a better choice. Sascha On Fri, Jan 8, 2010 at 7:38 AM, Tony yellowjacketl...@gmail.com wrote: Is there some way we can disable (abort install action) if someone were to launch our msi with the /a (administrative install) or /f (repair) options? We can hide the actions in the UI, but when launched via command-line they can still occur, we'd like to disable them for now. -- Tony -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing
[WiX-users] Is there a way to install an https-bound web site with an SSL certificate that is already on the box?
I saw one thread on this in the archives with no response. So, I figured the time may be ripe to ask again. I have an installation for a web site that is working really well so far except for this one little snag. I've plumbed everything in for the site I install to use https except for the certificate which - for security reasons - is already installed on the box by someone else. The install runs fine, but the web site doesn't work until I go into IIS and goose the authentication (or the binding if I'm in IIS 7) to attach it to the certificate. I've been trundling though the 3.0 docs for the IIS extensions and I've seen the Certificate and CertificateRef elements. I tried to be cute with these to see if I could define a Certificate with just the required attributes (Name, StoreLocation, and StoreName). I was hoping that would be enough to point the MSI in the direction of the existing certificate. But alas, the compiler barked at me for not having either BinaryKey or CertificatePath defined. So, my question is: Is there something I'm missing or perhaps a workaround to this situation? Thanks - Rich Daniel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] when files have been actually removed from install directory during uninstall process
Hi, I want to execute a custom action during uninstall process. Where should I put this in installexecutesequence ? Regards, Sanjay Rao -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] when files have been actually removed from install directory during uninstall process
Whereever you want, use add Installed as condition. This tells the installer to run the customaction if the application is being uninstalled. Best regards, Sebastian Brand sebast...@instyler.com Geisenfelder Str. 53a 85053 Ingolstadt, Germany EU VAT ID: DE219712370 Phone: +49 841 4544567 www.instyler.com http://www.instyler.com/ Travel add-in for Outlook http://www.traveladdin.com/ : Add travel and return times to your calendar. Instyler Setup http://www.instyler.com/ : Create WiX-based MSI installations, elegantly. Sebastianbrand.com http://www.sebastianbrand.com/ : blogging about software development, deployment and productivity -Original Message- From: Sanjay Rao [mailto:s...@noida.interrasystems.com] Sent: Friday, January 08, 2010 06:34 To: General discussion for Windows Installer XML toolset.; Windows Installer XML toolset developer mailing list Subject: [WiX-users] when files have been actually removed from install directory during uninstall process Hi, I want to execute a custom action during uninstall process. Where should I put this in installexecutesequence ? Regards, Sanjay Rao -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list mailto:WiX-users@lists.sourceforge.net WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Is there a way to install an https-bound web site with an SSL certificate that is already on the box?
Hi Rich, I think the Certificate tags are for installing a new certificate, not using an existing. Rob? J Best regards, Sebastian Brand sebast...@instyler.com Geisenfelder Str. 53a 85053 Ingolstadt, Germany EU VAT ID: DE219712370 Phone: +49 841 4544567 www.instyler.com http://www.instyler.com/ Travel add-in for Outlook http://www.traveladdin.com/ : Add travel and return times to your calendar. Instyler Setup http://www.instyler.com/ : Create WiX-based MSI installations, elegantly. Sebastianbrand.com http://www.sebastianbrand.com/ : blogging about software development, deployment and productivity -Original Message- From: Rich Daniel [mailto:rdan...@microsoft.com] Sent: Friday, January 08, 2010 01:01 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Is there a way to install an https-bound web site with an SSL certificate that is already on the box? I saw one thread on this in the archives with no response. So, I figured the time may be ripe to ask again. I have an installation for a web site that is working really well so far except for this one little snag. I've plumbed everything in for the site I install to use https except for the certificate which - for security reasons - is already installed on the box by someone else. The install runs fine, but the web site doesn't work until I go into IIS and goose the authentication (or the binding if I'm in IIS 7) to attach it to the certificate. I've been trundling though the 3.0 docs for the IIS extensions and I've seen the Certificate and CertificateRef elements. I tried to be cute with these to see if I could define a Certificate with just the required attributes (Name, StoreLocation, and StoreName). I was hoping that would be enough to point the MSI in the direction of the existing certificate. But alas, the compiler barked at me for not having either BinaryKey or CertificatePath defined. So, my question is: Is there something I'm missing or perhaps a workaround to this situation? Thanks - Rich Daniel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list mailto:WiX-users@lists.sourceforge.net WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to add a custom dialog in uninstall process using Wix
Thanks for this detailed explanation. Sanjay, you'll have to create a custom action that shows your dialog and then run this custom action from the MSI. The dialog itself is within the custom action DLL. So when you create the custom action from the C++ template, just add a Windows form dialog there. This is not a dialog from the MSI file. Best regards, Sebastian Brand sebast...@instyler.com Geisenfelder Str. 53a 85053 Ingolstadt, Germany EU VAT ID: DE219712370 Phone: +49 841 4544567 www.instyler.com http://www.instyler.com/ Travel add-in for Outlook http://www.traveladdin.com/ : Add travel and return times to your calendar. Instyler Setup http://www.instyler.com/ : Create WiX-based MSI installations, elegantly. Sebastianbrand.com http://www.sebastianbrand.com/ : blogging about software development, deployment and productivity -Original Message- From: Blair [mailto:os...@live.com] Sent: Thursday, January 07, 2010 23:28 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] How to add a custom dialog in uninstall process using Wix Dialogs (and dialog sequences) can always be easily added to be shown during uninstallations (that isn't usually the problem). It is done the same way dialog sequences are added to installations and to change transactions. The issue comes from the following: There are 4 levels of UI that can be requested for Windows Installer transactions, and different tools that may interact with your MSI will request different ones at different times. They are (see http://msdn.microsoft.com/library/aa372391.aspx http://msdn.microsoft.com/library/aa372391.aspx): * Full UI (shows everything) * Reduced UI (no modal dialogs - you shouldn't stop and wait for responses to any questions). Modal error dialogs are acceptable, however. * Basic UI (only built-in dialogs shown, no dialogs from the MSI are to be shown) * None (no UI at all) Windows Installer doesn't care which level is used when, but it is expected by all tools that the UI levels will be honored. Creating and showing dialogs from custom actions is one sure way of violating those levels and breaks administrative tools that work with Windows Installer packages, especially in corporate scenarios. The reason this is an issue is this: * When you double-click an MSI file from Windows Explorer, msiexec.exe is called with just the file as a command-line parameter. MsiExec defaults to Full UI. * When you select your installation from the Programs and Features window (aka Add/Remove Programs) and select an operation, what you get depends on the operation: * Modify: Full UI * Repair: Basic UI * Remove: Basic UI (after showing its own dialog box for confirmation) Yes, there is an UninstallString value in the registry for your installation, and if you run that string you will get Full UI, however, for MSI packages the Programs and Features window ignores that registry key. The UI level from that window (which is how most removals are performed) cannot be configured. Thus, most removals can't stop and ask the user for removal instructions/guidance without breaking the UI rules above and causing problems with GPO and other related tools. -Original Message- From: Sanjay Rao [mailto:s...@noida.interrasystems.com] Sent: Thursday, January 07, 2010 4:01 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to add a custom dialog in uninstall process using Wix I am not aware, how to show dialogs via custom actions. Please help with some sample code. Thanks Regards, Sanjay Rao Sebastian Brand (Instyler Software) wrote: You may only show dialogs during uninstallation via a custom action, the dialogs from the msi won't be shown. Best regards, Sebastian Brand mailto:sebast...@instyler.com sebast...@instyler.com Geisenfelder Str. 53a 85053 Ingolstadt, Germany EU VAT ID: DE219712370 Phone: +49 841 4544567 http://www.instyler.com www.instyler.com http://www.instyler.com/ http://www.instyler.com/ Travel add-in for Outlook http://www.traveladdin.com/ http://www.traveladdin.com/ : Add travel and return times to your calendar. Instyler Setup http://www.instyler.com/ http://www.instyler.com/ : Create WiX-based MSI installations, elegantly. Sebastianbrand.com http://www.sebastianbrand.com/ http://www.sebastianbrand.com/ : blogging about software development, deployment and productivity -Original Message- From: Sanjay Rao [mailto:s...@noida.interrasystems.com] Sent: Thursday, January 07, 2010 10:52 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] How to add a custom dialog in uninstall
Re: [WiX-users] Is there a way to install an https-bound web site with an SSL certificate that is already on the box?
The current custom actions require the certificate be supplied in the MSI. I think that would be a great feature request, or possibly even better, a contribution. -Original Message- From: Rich Daniel [mailto:rdan...@microsoft.com] Sent: Thursday, January 07, 2010 4:01 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Is there a way to install an https-bound web site with an SSL certificate that is already on the box? I saw one thread on this in the archives with no response. So, I figured the time may be ripe to ask again. I have an installation for a web site that is working really well so far except for this one little snag. I've plumbed everything in for the site I install to use https except for the certificate which - for security reasons - is already installed on the box by someone else. The install runs fine, but the web site doesn't work until I go into IIS and goose the authentication (or the binding if I'm in IIS 7) to attach it to the certificate. I've been trundling though the 3.0 docs for the IIS extensions and I've seen the Certificate and CertificateRef elements. I tried to be cute with these to see if I could define a Certificate with just the required attributes (Name, StoreLocation, and StoreName). I was hoping that would be enough to point the MSI in the direction of the existing certificate. But alas, the compiler barked at me for not having either BinaryKey or CertificatePath defined. So, my question is: Is there something I'm missing or perhaps a workaround to this situation? Thanks - Rich Daniel -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Showing actual MSI name on Windows UAC dialog
Whenever I execute/run my MSI on Windows VISTA / Win 7, Windows shows a UAC message asking: 'Do you want to allow the following program to install software on the computer? Program name: Some random number.msi Why does the program name specify some random number like 'a62738.msi'? Is there any way by which I can make it show my MSI's actual name like 'MyProduct.msi'? I think I need to set some MSI property, which I am not doing. Please let me know how to do that. Thanks, With Regards, // Sudripta Nandy -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Disable repair and admin setup...
repair cannot be disabled in Windows Installer due to the way it is put together. The best you can hope for is to reject an attempt to repair with an error message directing the user to remove-the-reinstall. -Original Message- From: Tony [mailto:yellowjacketl...@gmail.com] Sent: Thursday, January 07, 2010 4:42 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Disable repair and admin setup... Ooops! I replied directly rather than to the list... We've just never seen a need to support repair. That entails extensive testing by an already over-worked QA staff. All of our configuration information is in databases and we never remove databases during upgrade and/or uninstalls. So, if something really needs to be fixed just uninstall/install. I know that I personally never, ever do a repair. It just scares me and I don't trust it. Way too many what ifs. On Thu, Jan 7, 2010 at 6:51 PM, Sascha Beaumont sascha.beaum...@gmail.com wrote: Tony, I'm echoing Phil and Blair here.. Phil wrote: What is the problem that you believe disabling repair will solve? Blair wrote: If you have custom actions or other issues that break when repair is run, you should seek to fix those instead of disabling repair You shouldn't have to support repair, if repairing your installation breaks something then you're probably doing something wrong and you should be fixing the underlying issue rather than preventing repair. Custom Actions aside, try to think of your MSI as a description of how the system should look. When the system doesn't match the MSI, a repair is initiated. If you want an xcopy type setup, there are alternatives. Sascha On Fri, Jan 8, 2010 at 10:28 AM, Tony yellowjacketl...@gmail.com wrote: We never patch, so that won't be an issue. Thanks for the suggestion regarding admin installs. In the past we have never really supported repair either. So, we strive to prevent it from being triggered. We always use the ARPNOREPAIR, but the question of automated repair came up and we noticed it is still possible to trigger a repair action via that mechanism. We are trying to prevent repair not abort it as I might have suggested above. On Thu, Jan 7, 2010 at 6:01 PM, Blair os...@live.com wrote: You could simply drop the AdminExecuteSequence (and AdminUISequence) tables. That would prevent administrative installations. I also echo the question of why. Disabling repair is a bigger why?. If you are referring to the Repair button in the Programs and Features window just add the ARPNOREPAIR property Property Id=ARPNOREPAIR Value=1/ to your Product element. That will still allow triggered repairs based on broken installs as well as patching and non-major upgrades, but I personally prefer to see products that allow Repair from the Programs and Features window. If you have custom actions or other issues that break when repair is run, you should seek to fix those instead of disabling repair. Those issues aren't just repair issues, they are also upgrade issues (and possibly even remove issues) that should never be shipped until you fix them. -Original Message- From: Sascha Beaumont [mailto:sascha.beaum...@gmail.com] Sent: Thursday, January 07, 2010 1:49 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Disable repair and admin setup... I'm not too familiar with Administrative installs, but I would assume you could condition something in the AdminExecuteSequence and AdminUISequence to abort the install. Aborting if a repair is triggered sounds like a very strange request, what if your KeyPaths are damaged and you have advertised shortcuts? Windows Installer can no longer repair them and your app would likely fail to launch. The 'repair' functionality of Windows Installer is part of why you would choose to use MSI in the first place. If you're trying to bypass the resiliency features then maybe a non-MSI setup would be a better choice. Sascha On Fri, Jan 8, 2010 at 7:38 AM, Tony yellowjacketl...@gmail.com wrote: Is there some way we can disable (abort install action) if someone were to launch our msi with the /a (administrative install) or /f (repair) options? We can hide the actions in the UI, but when launched via command-line they can still occur, we'd like to disable them for now. -- Tony -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] when files have been actually removed from install directory during uninstall process
Installed as a condition will also run it when the application is being patched or repaired. Use REMOVE if the removal of any feature is reason to run your custom action. Have Windows Installer search the value of REMOVE for the name of the related feature (or for the term ALL) to be more robust. Or, if the custom action is scheduled after CostFinalize, use the feature install action syntax for the most robust. -Original Message- From: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com] Sent: Thursday, January 07, 2010 10:50 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] when files have been actually removed from install directory during uninstall process Whereever you want, use add Installed as condition. This tells the installer to run the customaction if the application is being uninstalled. Best regards, Sebastian Brand sebast...@instyler.com Geisenfelder Str. 53a 85053 Ingolstadt, Germany EU VAT ID: DE219712370 Phone: +49 841 4544567 www.instyler.com http://www.instyler.com/ Travel add-in for Outlook http://www.traveladdin.com/ : Add travel and return times to your calendar. Instyler Setup http://www.instyler.com/ : Create WiX-based MSI installations, elegantly. Sebastianbrand.com http://www.sebastianbrand.com/ : blogging about software development, deployment and productivity -Original Message- From: Sanjay Rao [mailto:s...@noida.interrasystems.com] Sent: Friday, January 08, 2010 06:34 To: General discussion for Windows Installer XML toolset.; Windows Installer XML toolset developer mailing list Subject: [WiX-users] when files have been actually removed from install directory during uninstall process Hi, I want to execute a custom action during uninstall process. Where should I put this in installexecutesequence ? Regards, Sanjay Rao -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list mailto:WiX-users@lists.sourceforge.net WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
