[WiX-users] Separate ExitDialog for Uninstall
Hi, I'm building the new win32 installer for Subversion with WiX but I've struck one snag. I would like to display a different dialog for install, uninstall, and possibly repair. I have customised the ExitDialog to show a nice post-install message for users, but obviously upon uninstall it wouldn't be logical to show the same post-install message. I have tried all kinds of combinations of conditions but cannot get this dialog to change. There has been very positive feedback from the Subversion community for the switch over to WiX and having an MSI installer instead of an exe installer. I am using SharpDevelop 3 as the WiX installer build tool. Can anyone assist? Regards, Troy Simpson Subversion Win32 Installer Maintainer ( SWIM?? ;) ) - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Separate ExitDialog for Uninstall
If I were you, I would play with InstallUISequence where some variations could yield the expected results. This is how I display a Firewall Dialog which adds some applications to the Windows Firewall after installation. Normally, the ExitDlg would be displayed when finishing the installation, but I needed it customized. Show Dialog=FirewallDlg Sequence=7999 ![CDATA[ ((VersionNT = 501 And ServicePackLevel = 2) Or (VersionNT = 502 And ServicePackLevel = 1) Or (VersionNT = 600)) And SomeLongCondition And Not EXISTINGPRODUCTS ]] /Show Show Dialog=ExitDlg OnExit=success ![CDATA[ Not ( ((VersionNT = 501 And ServicePackLevel = 2) Or (VersionNT = 502 And ServicePackLevel = 1) Or (VersionNT = 600)) And SomeLongCondition And Not EXISTINGPRODUCTS ) ]] /Show As long as you have Sequence and Conditions, there should be a way. Troy Simpson wrote: Hi, I'm building the new win32 installer for Subversion with WiX but I've struck one snag. I would like to display a different dialog for install, uninstall, and possibly repair. I have customised the ExitDialog to show a nice post-install message for users, but obviously upon uninstall it wouldn't be logical to show the same post-install message. I have tried all kinds of combinations of conditions but cannot get this dialog to change. There has been very positive feedback from the Subversion community for the switch over to WiX and having an MSI installer instead of an exe installer. I am using SharpDevelop 3 as the WiX installer build tool. Can anyone assist? Regards, Troy Simpson Subversion Win32 Installer Maintainer ( SWIM?? ;) ) - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Separate ExitDialog for Uninstall
Or you can use the same ExitDlg and customize the elements inside it like bitmaps, static text, position of elements based on conditions. Control Id=Description1 Type=Text X=135 Y=130 Width=220 Height=40 Text=For new users, we recommend that you read the quick guide located on the web. Click on the Finish button to exit the Setup Wizard. Transparent=yes Condition Action=showNot EXISTINGPRODUCTS/Condition Condition Action=hide1/Condition /Control Control Id=Description2 Type=Text X=135 Y=130 Width=220 Height=40 Text=The Upgrade process completed. Transparent=yes Condition Action=showEXISTINGPRODUCTS/Condition Condition Action=hide1/Condition /Control Calin Iaru wrote: If I were you, I would play with InstallUISequence where some variations could yield the expected results. This is how I display a Firewall Dialog which adds some applications to the Windows Firewall after installation. Normally, the ExitDlg would be displayed when finishing the installation, but I needed it customized. Show Dialog=FirewallDlg Sequence=7999 ![CDATA[ ((VersionNT = 501 And ServicePackLevel = 2) Or (VersionNT = 502 And ServicePackLevel = 1) Or (VersionNT = 600)) And SomeLongCondition And Not EXISTINGPRODUCTS ]] /Show Show Dialog=ExitDlg OnExit=success ![CDATA[ Not ( ((VersionNT = 501 And ServicePackLevel = 2) Or (VersionNT = 502 And ServicePackLevel = 1) Or (VersionNT = 600)) And SomeLongCondition And Not EXISTINGPRODUCTS ) ]] /Show As long as you have Sequence and Conditions, there should be a way. Troy Simpson wrote: Hi, I'm building the new win32 installer for Subversion with WiX but I've struck one snag. I would like to display a different dialog for install, uninstall, and possibly repair. I have customised the ExitDialog to show a nice post-install message for users, but obviously upon uninstall it wouldn't be logical to show the same post-install message. I have tried all kinds of combinations of conditions but cannot get this dialog to change. There has been very positive feedback from the Subversion community for the switch over to WiX and having an MSI installer instead of an exe installer. I am using SharpDevelop 3 as the WiX installer build tool. Can anyone assist? Regards, Troy Simpson Subversion Win32 Installer Maintainer ( SWIM?? ;) ) - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patch build with GAC update
That sounds like a bug to me, I would add it to the WiX bug database. Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] From: [EMAIL PROTECTED] on behalf of wixuser1105 Sent: Fri 20/06/2008 02:09 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Patch build with GAC update msp file has only 2 tables, MsiPatchMetadata and MsiPatchSequence. but the baseline and the upgraded msi files has fileversion row in tghe MsiAssemblyName table currectly. Sajid. That does show that the file is not being replaced. I am wondering whether the patch generating tool is doing the equivalent of the -fv. Can you open the patch in Orca and check that the FileVersion row is in the MsiAssemblyName table. Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Patch-build-with-GAC-update-tp17880093p18021195.html Sent from the wix-users mailing list archive at Nabble.com. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Removing registry keys via loop/enumeration...
Basically you can use registry search for this, in the example below I am searching for a directory in the registry to exist. To Delete just Action=remove. I don't know if registry search provides wildcard. Property Id=INSTALLDIR Value='C:\Nothing' RegistrySearch Id='ToSearch' Type='raw' Root='HKLM' Key='Software\[RegCompanyPart]\MyPoductDir ' Name='MyDirToSearch' / /Property Registry Id=ToSearch Action=remove / This should work for, but I don't know how to use wildcards or something in registry search. Martin Lierschof -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Heitor Tome Gesendet: Donnerstag, 19. Juni 2008 19:55 An: wix-users@lists.sourceforge.net Betreff: [WiX-users] Removing registry keys via loop/enumeration... Hi there, I have an installer that needs to remove registry keys before installing another registry key. Basically, I need to enumerate all subkeys of a specific key, find out if a specific word is in the key name and if so remove the registry key. Could anyone help me find out what is the best way to accomplish this with WiX? I am using the stable version. I was thinking about a C++ DLL to accomplish this task but wanted to find out first if there is already something in WiX to help me doing this. Thanks! - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Separate ExitDialog for Uninstall
Thanks for the suggestions Calin, Preferably, I'd like to have the condition in the modified ExitDlg - I've made a copy of it and using that instead. The existingproducts condition did not seem to make any difference, the control code is as follows: Control Id=PostText Type=ScrollableText X=20 Y=70 Width=330 Height=151 Sunken=yes TabSkip=no Text SourceFile=!(wix.WixUIPostRtf=$(var.postRtf)) /Text Condition Action=showEXISTINGPRODUCTS/Condition /Control Is there anything jumping out there that can be tweaked? Troy -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 5:49 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall Or you can use the same ExitDlg and customize the elements inside it like bitmaps, static text, position of elements based on conditions. Control Id=Description1 Type=Text X=135 Y=130 Width=220 Height=40 Text=For new users, we recommend that you read the quick guide located on the web. Click on the Finish button to exit the Setup Wizard. Transparent=yes Condition Action=showNot EXISTINGPRODUCTS/Condition Condition Action=hide1/Condition /Control Control Id=Description2 Type=Text X=135 Y=130 Width=220 Height=40 Text=The Upgrade process completed. Transparent=yes Condition Action=showEXISTINGPRODUCTS/Condition Condition Action=hide1/Condition /Control Calin Iaru wrote: If I were you, I would play with InstallUISequence where some variations could yield the expected results. This is how I display a Firewall Dialog which adds some applications to the Windows Firewall after installation. Normally, the ExitDlg would be displayed when finishing the installation, but I needed it customized. Show Dialog=FirewallDlg Sequence=7999 ![CDATA[ ((VersionNT = 501 And ServicePackLevel = 2) Or (VersionNT = 502 And ServicePackLevel = 1) Or (VersionNT = 600)) And SomeLongCondition And Not EXISTINGPRODUCTS ]] /Show Show Dialog=ExitDlg OnExit=success ![CDATA[ Not ( ((VersionNT = 501 And ServicePackLevel = 2) Or (VersionNT = 502 And ServicePackLevel = 1) Or (VersionNT = 600)) And SomeLongCondition And Not EXISTINGPRODUCTS ) ]] /Show As long as you have Sequence and Conditions, there should be a way. Troy Simpson wrote: Hi, I'm building the new win32 installer for Subversion with WiX but I've struck one snag. I would like to display a different dialog for install, uninstall, and possibly repair. I have customised the ExitDialog to show a nice post-install message for users, but obviously upon uninstall it wouldn't be logical to show the same post-install message. I have tried all kinds of combinations of conditions but cannot get this dialog to change. There has been very positive feedback from the Subversion community for the switch over to WiX and having an MSI installer instead of an exe installer. I am using SharpDevelop 3 as the WiX installer build tool. Can anyone assist? Regards, Troy Simpson Subversion Win32 Installer Maintainer ( SWIM?? ;) ) - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users --- -- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php
[WiX-users] Passing the 'installdir' to a custom action in modified format
Hi, I am facing a problem sending a string as a command line argument to a custom action which is a c++ build. Actually I need to send the Installation directory to the custom action. Suppose my user chooses installation directory as C:\Program Files\XYZ. But my custom action which is a c++ executable program needs the path as C:\\Program Files\\XYZ How do I convert 'C:\Program Files\XYZ' to 'C:\\Program Files\\XYZ' within the installer?? Thanks, Akshat - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Separate ExitDialog for Uninstall
EXISTINGPRODUCTS was a suggestion; what you need to do is to use a different property that when set, will show a different dialog control. For instance, if the user does an uninstall, use the REMOVE=ALL condition. Troy Simpson wrote: Thanks for the suggestions Calin, Preferably, I'd like to have the condition in the modified ExitDlg - I've made a copy of it and using that instead. The existingproducts condition did not seem to make any difference, the control code is as follows: Control Id=PostText Type=ScrollableText X=20 Y=70 Width=330 Height=151 Sunken=yes TabSkip=no Text SourceFile=!(wix.WixUIPostRtf=$(var.postRtf)) /Text Condition Action=showEXISTINGPRODUCTS/Condition /Control Is there anything jumping out there that can be tweaked? Troy -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 5:49 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall Or you can use the same ExitDlg and customize the elements inside it like bitmaps, static text, position of elements based on conditions. Control Id=Description1 Type=Text X=135 Y=130 Width=220 Height=40 Text=For new users, we recommend that you read the quick guide located on the web. Click on the Finish button to exit the Setup Wizard. Transparent=yes Condition Action=showNot EXISTINGPRODUCTS/Condition Condition Action=hide1/Condition /Control Control Id=Description2 Type=Text X=135 Y=130 Width=220 Height=40 Text=The Upgrade process completed. Transparent=yes Condition Action=showEXISTINGPRODUCTS/Condition Condition Action=hide1/Condition /Control Calin Iaru wrote: If I were you, I would play with InstallUISequence where some variations could yield the expected results. This is how I display a Firewall Dialog which adds some applications to the Windows Firewall after installation. Normally, the ExitDlg would be displayed when finishing the installation, but I needed it customized. Show Dialog=FirewallDlg Sequence=7999 ![CDATA[ ((VersionNT = 501 And ServicePackLevel = 2) Or (VersionNT = 502 And ServicePackLevel = 1) Or (VersionNT = 600)) And SomeLongCondition And Not EXISTINGPRODUCTS ]] /Show Show Dialog=ExitDlg OnExit=success ![CDATA[ Not ( ((VersionNT = 501 And ServicePackLevel = 2) Or (VersionNT = 502 And ServicePackLevel = 1) Or (VersionNT = 600)) And SomeLongCondition And Not EXISTINGPRODUCTS ) ]] /Show As long as you have Sequence and Conditions, there should be a way. Troy Simpson wrote: Hi, I'm building the new win32 installer for Subversion with WiX but I've struck one snag. I would like to display a different dialog for install, uninstall, and possibly repair. I have customised the ExitDialog to show a nice post-install message for users, but obviously upon uninstall it wouldn't be logical to show the same post-install message. I have tried all kinds of combinations of conditions but cannot get this dialog to change. There has been very positive feedback from the Subversion community for the switch over to WiX and having an MSI installer instead of an exe installer. I am using SharpDevelop 3 as the WiX installer build tool. Can anyone assist? Regards, Troy Simpson Subversion Win32 Installer Maintainer ( SWIM?? ;) ) - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users --- -- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list
Re: [WiX-users] Separate ExitDialog for Uninstall
The Remove=All didn't work, I had tried variations of that previously. I looked at the Remove button on the maintenance dialog and the property that is being set is WixUI_InstallMode, and the value is Remove, so I tried the condition: Not WixUI_InstallMode=Remove That did not work either. I have tried many, many variations, and none have worked. I'm sure I'm doing something silly though. I have uploaded my wix build project to here: http://www.ebswift.com/temp/buildsubversion.zip It doesn't include any of the subversion binaries so it won't build, but the files are there. In the BuildSubversion\WixDialog folder you will see the PostDlg.wxs that I am trying to get the condition working in. -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 6:43 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall EXISTINGPRODUCTS was a suggestion; what you need to do is to use a different property that when set, will show a different dialog control. For instance, if the user does an uninstall, use the REMOVE=ALL condition. Troy Simpson wrote: Thanks for the suggestions Calin, Preferably, I'd like to have the condition in the modified ExitDlg - I've made a copy of it and using that instead. The existingproducts condition did not seem to make any difference, the control code is as follows: Control Id=PostText Type=ScrollableText X=20 Y=70 Width=330 Height=151 Sunken=yes TabSkip=no Text SourceFile=!(wix.WixUIPostRtf=$(var.postRtf)) /Text Condition Action=showEXISTINGPRODUCTS/Condition /Control Is there anything jumping out there that can be tweaked? Troy -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 5:49 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall Or you can use the same ExitDlg and customize the elements inside it like bitmaps, static text, position of elements based on conditions. Control Id=Description1 Type=Text X=135 Y=130 Width=220 Height=40 Text=For new users, we recommend that you read the quick guide located on the web. Click on the Finish button to exit the Setup Wizard. Transparent=yes Condition Action=showNot EXISTINGPRODUCTS/Condition Condition Action=hide1/Condition /Control Control Id=Description2 Type=Text X=135 Y=130 Width=220 Height=40 Text=The Upgrade process completed. Transparent=yes Condition Action=showEXISTINGPRODUCTS/Condition Condition Action=hide1/Condition /Control Calin Iaru wrote: If I were you, I would play with InstallUISequence where some variations could yield the expected results. This is how I display a Firewall Dialog which adds some applications to the Windows Firewall after installation. Normally, the ExitDlg would be displayed when finishing the installation, but I needed it customized. Show Dialog=FirewallDlg Sequence=7999 ![CDATA[ ((VersionNT = 501 And ServicePackLevel = 2) Or (VersionNT = 502 And ServicePackLevel = 1) Or (VersionNT = 600)) And SomeLongCondition And Not EXISTINGPRODUCTS ]] /Show Show Dialog=ExitDlg OnExit=success ![CDATA[ Not ( ((VersionNT = 501 And ServicePackLevel = 2) Or (VersionNT = 502 And ServicePackLevel = 1) Or (VersionNT = 600)) And SomeLongCondition And Not EXISTINGPRODUCTS ) ]] /Show As long as you have Sequence and Conditions, there should be a way. Troy Simpson wrote: Hi, I'm building the new win32 installer for Subversion with WiX but I've struck one snag. I would like to display a different dialog for install, uninstall, and possibly repair. I have customised the ExitDialog to show a nice post-install message for users, but obviously upon uninstall it wouldn't be logical to show the same post-install message. I have tried all kinds of combinations of conditions but cannot get this dialog to change. There has been very positive feedback from the Subversion community for the switch over to WiX and having an MSI installer instead of an exe installer. I am using SharpDevelop 3 as the WiX installer build tool. Can anyone assist? Regards, Troy Simpson Subversion Win32 Installer Maintainer ( SWIM?? ;) ) -- -- - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about
Re: [WiX-users] Separate ExitDialog for Uninstall
There is a difference between REMOVE and Remove - the first one is a public property, the second is a private: http://msdn.microsoft.com/en-us/library/aa371245(VS.85).aspx I will let others to continue on this issue. Perhaps I will look at your project. Troy Simpson wrote: The Remove=All didn't work, I had tried variations of that previously. I looked at the Remove button on the maintenance dialog and the property that is being set is WixUI_InstallMode, and the value is Remove, so I tried the condition: Not WixUI_InstallMode=Remove That did not work either. I have tried many, many variations, and none have worked. I'm sure I'm doing something silly though. I have uploaded my wix build project to here: http://www.ebswift.com/temp/buildsubversion.zip It doesn't include any of the subversion binaries so it won't build, but the files are there. In the BuildSubversion\WixDialog folder you will see the PostDlg.wxs that I am trying to get the condition working in. -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 6:43 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall EXISTINGPRODUCTS was a suggestion; what you need to do is to use a different property that when set, will show a different dialog control. For instance, if the user does an uninstall, use the REMOVE=ALL condition. Troy Simpson wrote: Thanks for the suggestions Calin, Preferably, I'd like to have the condition in the modified ExitDlg - I've made a copy of it and using that instead. The existingproducts condition did not seem to make any difference, the control code is as follows: Control Id=PostText Type=ScrollableText X=20 Y=70 Width=330 Height=151 Sunken=yes TabSkip=no Text SourceFile=!(wix.WixUIPostRtf=$(var.postRtf)) /Text Condition Action=showEXISTINGPRODUCTS/Condition /Control Is there anything jumping out there that can be tweaked? Troy -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 5:49 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall Or you can use the same ExitDlg and customize the elements inside it like bitmaps, static text, position of elements based on conditions. Control Id=Description1 Type=Text X=135 Y=130 Width=220 Height=40 Text=For new users, we recommend that you read the quick guide located on the web. Click on the Finish button to exit the Setup Wizard. Transparent=yes Condition Action=showNot EXISTINGPRODUCTS/Condition Condition Action=hide1/Condition /Control Control Id=Description2 Type=Text X=135 Y=130 Width=220 Height=40 Text=The Upgrade process completed. Transparent=yes Condition Action=showEXISTINGPRODUCTS/Condition Condition Action=hide1/Condition /Control Calin Iaru wrote: If I were you, I would play with InstallUISequence where some variations could yield the expected results. This is how I display a Firewall Dialog which adds some applications to the Windows Firewall after installation. Normally, the ExitDlg would be displayed when finishing the installation, but I needed it customized. Show Dialog=FirewallDlg Sequence=7999 ![CDATA[ ((VersionNT = 501 And ServicePackLevel = 2) Or (VersionNT = 502 And ServicePackLevel = 1) Or (VersionNT = 600)) And SomeLongCondition And Not EXISTINGPRODUCTS ]] /Show Show Dialog=ExitDlg OnExit=success ![CDATA[ Not ( ((VersionNT = 501 And ServicePackLevel = 2) Or (VersionNT = 502 And ServicePackLevel = 1) Or (VersionNT = 600)) And SomeLongCondition And Not EXISTINGPRODUCTS ) ]] /Show As long as you have Sequence and Conditions, there should be a way. Troy Simpson wrote: Hi, I'm building the new win32 installer for Subversion with WiX but I've struck one snag. I would like to display a different dialog for install, uninstall, and possibly repair. I have customised the ExitDialog to show a nice post-install message for users, but obviously upon uninstall it wouldn't be logical to show the same post-install message. I have tried all kinds of combinations of conditions but cannot get this dialog to change. There has been very positive
Re: [WiX-users] Patch build with GAC update
I am new to WIX and MSI. can I use REINSTALLMODE to force replace assembly in the GAC? Neil Sleightholm wrote: That sounds like a bug to me, I would add it to the WiX bug database. Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Patch-build-with-GAC-update-tp17880093p18026392.html Sent from the wix-users mailing list archive at Nabble.com. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patch build with GAC update
I am afraid I don't know. Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] From: [EMAIL PROTECTED] on behalf of wixuser1105 Sent: Fri 20/06/2008 10:58 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Patch build with GAC update I am new to WIX and MSI. can I use REINSTALLMODE to force replace assembly in the GAC? Neil Sleightholm wrote: That sounds like a bug to me, I would add it to the WiX bug database. Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Patch-build-with-GAC-update-tp17880093p18026392.html Sent from the wix-users mailing list archive at Nabble.com. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Separate ExitDialog for Uninstall
I think I see where this is going, but hopefully it might be more intuitive. I can set a property based on whether the product is already installed, but what I need to do is retrieve the property value when the remove button is clicked. Given that the property set by the remove button is private, is there a way of also setting a public property value? i.e., can multiple properties be set by one button press? Or is that off the mark? Thanks for the help so far, this seems like a fairly fundamental thing and is the last remaining issue in my installer. -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 7:58 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall There is a difference between REMOVE and Remove - the first one is a public property, the second is a private: http://msdn.microsoft.com/en-us/library/aa371245(VS.85).aspx I will let others to continue on this issue. Perhaps I will look at your project. Troy Simpson wrote: The Remove=All didn't work, I had tried variations of that previously. I looked at the Remove button on the maintenance dialog and the property that is being set is WixUI_InstallMode, and the value is Remove, so I tried the condition: Not WixUI_InstallMode=Remove That did not work either. I have tried many, many variations, and none have worked. I'm sure I'm doing something silly though. I have uploaded my wix build project to here: http://www.ebswift.com/temp/buildsubversion.zip It doesn't include any of the subversion binaries so it won't build, but the files are there. In the BuildSubversion\WixDialog folder you will see the PostDlg.wxs that I am trying to get the condition working in. -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 6:43 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall EXISTINGPRODUCTS was a suggestion; what you need to do is to use a different property that when set, will show a different dialog control. For instance, if the user does an uninstall, use the REMOVE=ALL condition. Troy Simpson wrote: Thanks for the suggestions Calin, Preferably, I'd like to have the condition in the modified ExitDlg - I've made a copy of it and using that instead. The existingproducts condition did not seem to make any difference, the control code is as follows: Control Id=PostText Type=ScrollableText X=20 Y=70 Width=330 Height=151 Sunken=yes TabSkip=no Text SourceFile=!(wix.WixUIPostRtf=$(var.postRtf)) /Text Condition Action=showEXISTINGPRODUCTS/Condition /Control Is there anything jumping out there that can be tweaked? Troy -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 5:49 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall Or you can use the same ExitDlg and customize the elements inside it like bitmaps, static text, position of elements based on conditions. Control Id=Description1 Type=Text X=135 Y=130 Width=220 Height=40 Text=For new users, we recommend that you read the quick guide located on the web. Click on the Finish button to exit the Setup Wizard. Transparent=yes Condition Action=showNot EXISTINGPRODUCTS/Condition Condition Action=hide1/Condition /Control Control Id=Description2 Type=Text X=135 Y=130 Width=220 Height=40 Text=The Upgrade process completed. Transparent=yes Condition Action=showEXISTINGPRODUCTS/Condition Condition Action=hide1/Condition /Control Calin Iaru wrote: If I were you, I would play with InstallUISequence where some variations could yield the expected results. This is how I display a Firewall Dialog which adds some applications to the Windows Firewall after installation. Normally, the ExitDlg would be displayed when finishing the installation, but I needed it customized. Show Dialog=FirewallDlg Sequence=7999 ![CDATA[ ((VersionNT = 501 And ServicePackLevel = 2) Or (VersionNT = 502 And ServicePackLevel = 1) Or (VersionNT = 600)) And SomeLongCondition And Not EXISTINGPRODUCTS ]] /Show Show Dialog=ExitDlg OnExit=success ![CDATA[ Not ( ((VersionNT = 501 And ServicePackLevel = 2) Or (VersionNT = 502 And ServicePackLevel = 1) Or (VersionNT = 600))
[WiX-users] [wix-users] Windows Service (ServiceControl)
I have an issue with windows service startup. following is the WIX xml fragment. Component Id=C1 Guid=F504963A-BC48-4703-B978-B31CCDD0E3A5 File Id=WS1 Name=WS1.exe DiskId=1 Source=$(var.buildPath)\WS1.exe/File File Id=WS1.config Name=WS1.config DiskId=1 Source=$(var.buildPath)\WS1.exe.config/File ServiceInstall Id=WS1 DisplayName=WS1 Account=LocalSystem Type=ownProcess Start=auto Vital=yes Name=WS1 ErrorControl=normal /ServiceInstall ServiceControl Id=WS1 Name=WS1 Stop=both Start=install Remove=uninstall/ServiceControl /Component I get an error when the service starts. FileNotFOundException. Actuallty the WS1.exe.config has a custom Config section with a type WS1Config belogs to an assembly which will also be installed to the GAC in the same package. if I remove the attribute STart from SErviceControl and manually start the service after installation it works fine. right now I have written vbs to start all the windows services in the custom event. -- View this message in context: http://www.nabble.com/-wix-users--Windows-Service-%28ServiceControl%29-tp18026492p18026492.html Sent from the wix-users mailing list archive at Nabble.com. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] reading install path from registry for add-on
hi, i'm trying to write an installer for an addon. the dumb way, but i have to. i'm reading the main install path of the main/parent app from registry. it is stored there as a full path string like D:\Not Program Files\InstalledHereInstead\Foo App\ i read it using Property Id=INSTALLDIR RegistrySearch Id='mainprogdirsearch' Type='raw' Root='HKLM' Key='Software\Foo App\Setup Info' Name='locprogdir' / /Property and i'm guessing it gets read because a condition on INSTALLDIR is not triggered. but here's my problem: how do i then use this nice string path to actually specify the install location, that is otherwise and normally done by neatly nesting Directory-s one depth at the time thanks for your time end efforts in advance. jozsef koloszar, hungary - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Skip EULA (Wix3)
Hey, I'm working with Wix 3. I want to create a UI installer with WixUI_Mondo . Is there a possibility (configuration statement) to leave the License agreement out? Thanks for help, Peter Smit http://www.petersmit.eu - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Separate ExitDialog for Uninstall
I will not do the research for you - the link I sent shows the difference between a public and a private property. In short public properties are also properties that are set as a result of user interaction. What you are doing is not setting a property, but an event which is called Remove as in: Control Id=Remove Type=PushButton X=236 Y=243 Width=56 Height=17 Text=[ButtonText_Remove] Default=yes Publish Event=Remove Value=ALL![CDATA[OutOfDiskSpace 1]]/Publish Try with REMOVE=ALL condition once more. Troy Simpson wrote: I think I see where this is going, but hopefully it might be more intuitive. I can set a property based on whether the product is already installed, but what I need to do is retrieve the property value when the remove button is clicked. Given that the property set by the remove button is private, is there a way of also setting a public property value? i.e., can multiple properties be set by one button press? Or is that off the mark? Thanks for the help so far, this seems like a fairly fundamental thing and is the last remaining issue in my installer. -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 7:58 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall There is a difference between REMOVE and Remove - the first one is a public property, the second is a private: http://msdn.microsoft.com/en-us/library/aa371245(VS.85).aspx I will let others to continue on this issue. Perhaps I will look at your project. Troy Simpson wrote: The Remove=All didn't work, I had tried variations of that previously. I looked at the Remove button on the maintenance dialog and the property that is being set is WixUI_InstallMode, and the value is Remove, so I tried the condition: Not WixUI_InstallMode=Remove That did not work either. I have tried many, many variations, and none have worked. I'm sure I'm doing something silly though. I have uploaded my wix build project to here: http://www.ebswift.com/temp/buildsubversion.zip It doesn't include any of the subversion binaries so it won't build, but the files are there. In the BuildSubversion\WixDialog folder you will see the PostDlg.wxs that I am trying to get the condition working in. -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 6:43 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall EXISTINGPRODUCTS was a suggestion; what you need to do is to use a different property that when set, will show a different dialog control. For instance, if the user does an uninstall, use the REMOVE=ALL condition. Troy Simpson wrote: Thanks for the suggestions Calin, Preferably, I'd like to have the condition in the modified ExitDlg - I've made a copy of it and using that instead. The existingproducts condition did not seem to make any difference, the control code is as follows: Control Id=PostText Type=ScrollableText X=20 Y=70 Width=330 Height=151 Sunken=yes TabSkip=no Text SourceFile=!(wix.WixUIPostRtf=$(var.postRtf)) /Text Condition Action=showEXISTINGPRODUCTS/Condition /Control Is there anything jumping out there that can be tweaked? Troy -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 5:49 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall Or you can use the same ExitDlg and customize the elements inside it like bitmaps, static text, position of elements based on conditions. Control Id=Description1 Type=Text X=135 Y=130 Width=220 Height=40 Text=For new users, we recommend that you read the quick guide located on the web. Click on the Finish button to exit the Setup Wizard. Transparent=yes Condition Action=showNot EXISTINGPRODUCTS/Condition Condition Action=hide1/Condition /Control Control Id=Description2 Type=Text X=135 Y=130 Width=220 Height=40 Text=The Upgrade process completed. Transparent=yes Condition Action=showEXISTINGPRODUCTS/Condition Condition Action=hide1/Condition /Control Calin Iaru wrote:
Re: [WiX-users] reading install path from registry for add-on
You can use a Directory Id like a property. E.g. You can have Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Name=PFiles Directory Id=PRODUCTDIR Name=MyProduct ... Components ... /Directory /Directory /Directory You can then use a Custom Action (or I guess the RegSearch action directly) to set PRODUCTDIR like you would a normal property. All the child directories below it will also get resolved as expected. Rob Koloszar Jozsef wrote: hi, i'm trying to write an installer for an addon. the dumb way, but i have to. i'm reading the main install path of the main/parent app from registry. it is stored there as a full path string like D:\Not Program Files\InstalledHereInstead\Foo App\ i read it using Property Id=INSTALLDIR RegistrySearch Id='mainprogdirsearch' Type='raw' Root='HKLM' Key='Software\Foo App\Setup Info' Name='locprogdir' / /Property and i'm guessing it gets read because a condition on INSTALLDIR is not triggered. but here's my problem: how do i then use this nice string path to actually specify the install location, that is otherwise and normally done by neatly nesting Directory-s one depth at the time thanks for your time end efforts in advance. jozsef koloszar, hungary - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] DTF custom action questions
My installation creates and then interacts with a SQL Server database. Up until now, I've been able to do everything I need to do from WiX using the standard extensions, but now I'm facing a problem for which I need a custom action. I have to import some data into my database, but I need to modify it based on information gathered during the installation. Here are my questions: 1. How can I properly schedule my custom action to ensure it runs after my other SqlScripts and SqlStrings have been run? 2. How can I use data files (stored in the MSI with the Binary element*) in my custom action? I don't want to actually install them on the user's machine, just use them during the installation. 3. I'm having a hard time getting my head around how to correctly author and deploy a DTF custom action. Using Votive, I'm able to build the CA assemblies properly, but what do I need to add in my WiX project to make sure all of the elements are available to execute the custom action? DTF.chm has a good enough sample of C# code that I can follow the CA method creation, but can somebody point me to a sample fragment that includes all of the elements necessary to get a DTF CA to run? * I'm not wedded to using them as Binary streams in the MSI; if somebody has a better suggestion, please feel free to chime in. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Commercial products packaged by WiX toolset
Hello, I am planning to compile a list of well-known software applications packaged by WiX toolset. (MS or non-MS does not matter) Could you let this list know about the packages that you noticed built by WiX toolset? Thanks for the help. Husnu - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Commercial products packaged by WiX toolset
I did this one, www.viapost.com (still working on it, but live). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Husnu Kaplan Sent: 20 June 2008 14:35 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Commercial products packaged by WiX toolset Hello, I am planning to compile a list of well-known software applications packaged by WiX toolset. (MS or non-MS does not matter) Could you let this list know about the packages that you noticed built by WiX toolset? Thanks for the help. Husnu - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users No virus found in this incoming message. Checked by AVG. Version: 8.0.100 / Virus Database: 270.4.1/1510 - Release Date: 19/06/2008 15:21 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] DTF custom action questions
1. In your InstallExecuteSequence, you could schedule your CA relative to the WixSqlExtension CA like this: Custom Action=MySqlCA After=InstallSqlData ... You'll need to do the work in a deferred CA, because the WixSqlExtension CAs do their work in the deferred phase. But it is a common pattern to invoke (schedule) a deferred CA directly from an immediate CA, so in that case you only need to author the immediate CA scheduling in WiX. 2. From an immediate CA, you can read the data from the Binary table into either a Stream or a file: open a View on the Binary table, execute the View, fetch the Record, and then call one of the Record.GetStream() overloads. Then you'll need to pass this data to a deferred CA because an immediate CA should not modify system state and a deferred CA cannot read the MSI database. (And also because it needs to be after the InstallSqlData CA as mentioned above.) To pass that data, fill a CustomActionData object with the data and invoke the deferred CA with session.DoAction(deferredActionName, actionData). Then from within the deferred CA you can access that data as the session.CustomActionData property. Finally, don't forget about rollback and uninstall! 3. A DTF CA DLL is authored in WiX exactly like an unmanaged CA DLL. You need a Binary element for the DLL, a CustomAction element for each CA entrypoint, and a Custom Action=... to sequence each call in InstallExecuteSequence. When it comes to the MSI/WiX authoring, there are no additional elements you need to worry about just because the CA is managed or using DTF (other than perhaps a LaunchCondition to verify .NET is available). Hope this helps. -Jason- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Jim Sent: Friday, June 20, 2008 4:24 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] DTF custom action questions My installation creates and then interacts with a SQL Server database. Up until now, I've been able to do everything I need to do from WiX using the standard extensions, but now I'm facing a problem for which I need a custom action. I have to import some data into my database, but I need to modify it based on information gathered during the installation. Here are my questions: 1. How can I properly schedule my custom action to ensure it runs after my other SqlScripts and SqlStrings have been run? 2. How can I use data files (stored in the MSI with the Binary element*) in my custom action? I don't want to actually install them on the user's machine, just use them during the installation. 3. I'm having a hard time getting my head around how to correctly author and deploy a DTF custom action. Using Votive, I'm able to build the CA assemblies properly, but what do I need to add in my WiX project to make sure all of the elements are available to execute the custom action? DTF.chm has a good enough sample of C# code that I can follow the CA method creation, but can somebody point me to a sample fragment that includes all of the elements necessary to get a DTF CA to run? * I'm not wedded to using them as Binary streams in the MSI; if somebody has a better suggestion, please feel free to chime in. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Search for Installed Windows Component
Hi, Is there a way to search for installed windows components ? Suppose I have to search whether .Net is installed it or not. Can I do so without the use of custom actions? Regards, Akshat - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [wix-users] Windows Service (ServiceControl)
What Operating System is this on? I'm having a problem with services http://www.nabble.com/Service-Failing-to-Start-on-Vista-td18008909.html#a18008909 here Seems to be a Vista Issue mainly for me, with the service trying to start before all files and merge modules are installed. wixuser1105 wrote: I have an issue with windows service startup. following is the WIX xml fragment. Component Id=C1 Guid=F504963A-BC48-4703-B978-B31CCDD0E3A5 File Id=WS1 Name=WS1.exe DiskId=1 Source=$(var.buildPath)\WS1.exe/File File Id=WS1.config Name=WS1.config DiskId=1 Source=$(var.buildPath)\WS1.exe.config/File ServiceInstall Id=WS1 DisplayName=WS1 Account=LocalSystem Type=ownProcess Start=auto Vital=yes Name=WS1 ErrorControl=normal /ServiceInstall ServiceControl Id=WS1 Name=WS1 Stop=both Start=install Remove=uninstall/ServiceControl /Component I get an error when the service starts. FileNotFOundException. Actuallty the WS1.exe.config has a custom Config section with a type WS1Config belogs to an assembly which will also be installed to the GAC in the same package. if I remove the attribute STart from SErviceControl and manually start the service after installation it works fine. right now I have written vbs to start all the windows services in the custom event. -- View this message in context: http://www.nabble.com/-wix-users--Windows-Service-%28ServiceControl%29-tp18026492p18031279.html Sent from the wix-users mailing list archive at Nabble.com. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Votive support for VS 2005
Hi Rob and co, I have installed the 3.0.4214.0 version of Wix on my Windows 2003 SP2 machine (Visual Studio 2005). I created a new WiX project, and though the process created 4 files (Product.wxs, WixProject1.sln, WixProject2.suo, WixProject2.wixproj), it only shows Product.wxs in the editor window. There is no solution in the Solution Explorer, and the project is also not visible. I would like to offer my services to resolve this issue as it is now crucial for me to get this running before I get my colleagues to buy into WiX 3.0. Here is what I have so far: The ProjectAggregator2.msi installation failed. I have attached a log file generated by msiexec http://www.nabble.com/file/p18031954/ProjectAggregator2log.txt ProjectAggregator2log.txt Since I had run the ProjectAggregator2.msi from a previous build, I figured I could try and continue without it, so I ran the Wix3.msi (which worked fine). Then I selected File=New Project from within a new instance of Visual Studio, and selected WiX Project. The new project was built, but was not shown in the Solution Explorer. Please let me know if you need any more information Regards, Carl -- View this message in context: http://www.nabble.com/Votive-support-for-VS-2005-tp18031954p18031954.html Sent from the wix-users mailing list archive at Nabble.com. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Newbee - How to convert MSI into XML and back toWIX MSI?
Thanks Chris, using your solution I was able to create .wxs file from the MSI. But when I compile it using Candle, I receive the following errors (3 errors and 2 warnings): - C:\Working\Mesh\Admin\NewMesh.wxs(51664) : error CNDL0193 : The Directory/@Name attribute's value, 'Explorer.Xml', cannot be specified with attribute ShortName present. - C:\Working\Mesh\Admin\NewMesh.wxs(57848) : error CNDL0193 : The Directory/@Name attribute's value, 'TIBCO.EMS', cannot be specified with attribute ShortName present. - C:\Working\Mesh\Admin\NewMesh.wxs(50717) : error CNDL0206 : The 'TARGETDIR' directory has an illegal DefaultDir value of 'tqepgrb4|SOURCEDIR'. The DefaultDir value is created from the *Name attributes of the Directory element. The TARGETDIR directory is a special directory which must have its Name attribute set to 'SourceDir' or 'SOURCEDIR'. - C:\Working\Mesh\Admin\NewMesh.wxs(59099) : warning CNDL1077 : The 'DiskPrompt' Property contains '[ProductName]' in its value which is an illegal reference to another property. If this value is a string literal, not a property reference, please ignore this warning. To set a property with the value of another property, use a CustomAction with Property and Value attributes. - C:\Working\Mesh\Admin\NewMesh.wxs(59109) : warning CNDL1083 : The 'ProductID' property should not be directly authored because it will prevent the ValidateProductID standard action from performing any validation during the installation. This property will be set by the ValidateProductID standard action or control event. - I don't know what they means and there is no help/documentation on the WIX errors either! Please can you help here? If you want, I can forward the .wxs file. BTW, I am using the latest WIX (ver 3.0.2925.0). Regards Uttam -Original Message- From: Christopher Painter [mailto:[EMAIL PROTECTED] Sent: Thursday, June 19, 2008 4:35 PM To: General discussion for Windows Installer XML toolset.; Mathur, Uttam (GTS) Subject: RE: [WiX-users] Newbee - How to convert MSI into XML and back toWIX MSI? Basically you'd use dark and then do whatever refactoring you need to get it cleaned up. Without knowing your application/install I can't tell you what would be involved or how long it would take you. Maybe Rob Mensching could give you an architecture review to help you make that decision. Either way, make sure you get paid to do this. :-)Personally I discuss tool selection, source ownership and operational issues with all of my clients before making a bid on the project. If we can't come to an agreement, I pass on the work. I really wouldn't want to be in your shoes right now unless the client was firmly committed to funding the refactoring and you have the time to devote to the learning curve. Regards, Chris Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Thu, 6/19/08, Mathur, Uttam (GTS) [EMAIL PROTECTED] wrote: From: Mathur, Uttam (GTS) [EMAIL PROTECTED] Subject: RE: [WiX-users] Newbee - How to convert MSI into XML and back toWIX MSI? To: [EMAIL PROTECTED], General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Thursday, June 19, 2008, 3:12 PM Thanks. So what's the best way to achieve this? My client does not want to use Wise and we need to find out a way where my wise created MSI can be leveraged by them using WIX? TIA Warm Regards, Uttam Mathur -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Painter Sent: Thursday, June 19, 2008 4:08 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Newbee - How to convert MSI into XML and back toWIX MSI? Dark is the decompiler that authors wxs files but note, dark/candle/light don't really support roundtripping in a very easy way. It's really designed for people wanting to migrate to WiX and not go back so there is usually refactoring involved. For example, Wise drives dialogs with vbscript CA's from what I've seen. That's a no-no in WiX. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a
Re: [WiX-users] Skip EULA (Wix3)
I don't believe you can configure your way around it. You can, however, create your own custom variation of WixUI_Mondo, it's pretty easy to do. Here's how to do it: 1. download wix sourcecode via links from the wix homepage. 2. locate the wixlib folder from here: \wix-3.0.2925.0-sources\src\ext\UIExtension\wixlib and make a copy of the whole folder to somewhere else. 3. find WixUI_Mondo.wxs in your wixlib copied folder and make a copy of that file - rename it to whatever you like. Eg. WixUIMyMondo.wxs. 4. find and comment out or delete the following lines: Publish Dialog=LicenseAgreementDlg Control=Back Event=NewDialog Value=WelcomeDlg1/Publish Publish Dialog=LicenseAgreementDlg Control=Next Event=NewDialog Value=SetupTypeDlg Order=2LicenseAccepted = 1/Publish 5. make changes to back and next buttons to skip over the old LicenseAgreementDlg (change the Value attributes): Publish Dialog=WelcomeDlg Control=Next Event=NewDialog Value=SetupTypeDlg1/Publish Publish Dialog=SetupTypeDlg Control=Back Event=NewDialog Value= WelcomeDlg 1/Publish 6. compile your modified WixUI_Mondo: candle.exe WixUI_MyMondo.wxs lit.exe -out WixUI_MyMondo.wixlib 7. link your project to WixUI_MyMondo.wixlib instead of WixUI_Mondo.wixlib That should work. I'm only a newbie so hopefully I haven't lead you too far astray. Regards, Troy Simpson -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Peter Smit Sent: Friday, 20 June 2008 8:48 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Skip EULA (Wix3) Hey, I'm working with Wix 3. I want to create a UI installer with WixUI_Mondo . Is there a possibility (configuration statement) to leave the License agreement out? Thanks for help, Peter Smit http://www.petersmit.eu --- -- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixCA CAQuietExec does not support x64 - correct?
by daleq Apr 18, 2008; 02:28pm From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Friday, April 18, 2008 2:18 PM Actually, we *just* added 64-bit support (took for freakin' ever to put the build back together). I'm not sure CAQuietExec was made 64-bit since we only focused on the CAs that had known issues. If it doesn't feel free to open a bug with the below information. That sounds great! I'll take a look at 3.0.4014.0. Sorry for the long delay. I've just tried with 3.0.4214.0 and it does not seem to work. I've filed a bug here; https://sourceforge.net/tracker/?func=detailatid=642714aid=1998496gro up_id=105970 I assume that this may possibly be resolved in src\ca\wcautil\qtexec.cpp at this section; if (::CreateProcessW(NULL, wzCommand, // command line NULL, // security info NULL, // thread info TRUE, // inherit handles ::GetPriorityClass(::GetCurrentProcess()) | CREATE_NO_WINDOW, // creation flags NULL, // environment NULL, // cur dir oStartInfo, oProcInfo)) but I don't know enough C to fight my way out of a wet paper bag. smile/ Thanks, Dale - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Separate ExitDialog for Uninstall
Yes, you can create custom action that sets one property to the value of another. And you can Publish multiple DoAction events on button press. Examples: Property Id=INSTALLDIR Secure=yes / Property Id=WIXUI_INSTALLDIR Value=INSTALLDIR / Property Id=MY_PROP_TEMPFOLDER Secure=yes / CustomAction Id=My_CA_SetTemporaryFolder Property=MY_PROP_TEMPFOLDER Value=[TempFolder] Execute=oncePerProcess / Publish Dialog=OptionsDialog Control=Next Event=DoAction Value= My_CA_SetTemporaryFolder Order=1MY_PROP_SOMETHING=1/Publish Publish Dialog=OptionsDialog Control=Next Event=DoAction Value=MY_CA_SomethingElse Order=2/ -Original Message- From: Troy Simpson [mailto:[EMAIL PROTECTED] Sent: Friday, June 20, 2008 6:17 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Separate ExitDialog for Uninstall I think I see where this is going, but hopefully it might be more intuitive. I can set a property based on whether the product is already installed, but what I need to do is retrieve the property value when the remove button is clicked. Given that the property set by the remove button is private, is there a way of also setting a public property value? i.e., can multiple properties be set by one button press? Or is that off the mark? Thanks for the help so far, this seems like a fairly fundamental thing and is the last remaining issue in my installer. -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 7:58 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall There is a difference between REMOVE and Remove - the first one is a public property, the second is a private: http://msdn.microsoft.com/en-us/library/aa371245(VS.85).aspx I will let others to continue on this issue. Perhaps I will look at your project. Troy Simpson wrote: The Remove=All didn't work, I had tried variations of that previously. I looked at the Remove button on the maintenance dialog and the property that is being set is WixUI_InstallMode, and the value is Remove, so I tried the condition: Not WixUI_InstallMode=Remove That did not work either. I have tried many, many variations, and none have worked. I'm sure I'm doing something silly though. I have uploaded my wix build project to here: http://www.ebswift.com/temp/buildsubversion.zip It doesn't include any of the subversion binaries so it won't build, but the files are there. In the BuildSubversion\WixDialog folder you will see the PostDlg.wxs that I am trying to get the condition working in. -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 6:43 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall EXISTINGPRODUCTS was a suggestion; what you need to do is to use a different property that when set, will show a different dialog control. For instance, if the user does an uninstall, use the REMOVE=ALL condition. Troy Simpson wrote: Thanks for the suggestions Calin, Preferably, I'd like to have the condition in the modified ExitDlg - I've made a copy of it and using that instead. The existingproducts condition did not seem to make any difference, the control code is as follows: Control Id=PostText Type=ScrollableText X=20 Y=70 Width=330 Height=151 Sunken=yes TabSkip=no Text SourceFile=!(wix.WixUIPostRtf=$(var.postRtf)) /Text Condition Action=showEXISTINGPRODUCTS/Condition /Control Is there anything jumping out there that can be tweaked? Troy -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 5:49 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall Or you can use the same ExitDlg and customize the elements inside it like bitmaps, static text, position of elements based on conditions. Control Id=Description1 Type=Text X=135 Y=130 Width=220 Height=40 Text=For new users, we recommend that you read the quick guide located on the web. Click on the Finish button to exit the Setup Wizard. Transparent=yes Condition Action=showNot EXISTINGPRODUCTS/Condition Condition Action=hide1/Condition /Control Control Id=Description2 Type=Text X=135 Y=130 Width=220 Height=40 Text=The Upgrade process completed. Transparent=yes Condition Action=showEXISTINGPRODUCTS/Condition Condition Action=hide1/Condition
Re: [WiX-users] DTF custom action questions
Thanks Jason, this gets me most of the way to where I need. Let me see if I understand this correctly: * I create two CustomAction elements in my WiX project, one for the immediate custom action, one for the deferred. * Then, I schedule the immediate custom action using a Custom element in my WiX project under the InstallExecuteSequence element. * In my C# code for the immediate custom action, I place a session.DoAction() call using the name of my deferred CA in the Id attribute of my Custom element. I've tried this with WiX 3.0.4214 and when I attempt to install the resulting .msi, I get an error 2721 (Custom Action foo not found in the binary table stream) when the installer attempts to schedule the deferred action. Looking in orca, everything looks right in the CustomAction table, but I'm clearly missing something simple here. --Jim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Ginchereau Sent: Friday, June 20, 2008 9:50 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] DTF custom action questions 1. In your InstallExecuteSequence, you could schedule your CA relative to the WixSqlExtension CA like this: Custom Action=MySqlCA After=InstallSqlData ... You'll need to do the work in a deferred CA, because the WixSqlExtension CAs do their work in the deferred phase. But it is a common pattern to invoke (schedule) a deferred CA directly from an immediate CA, so in that case you only need to author the immediate CA scheduling in WiX. 2. From an immediate CA, you can read the data from the Binary table into either a Stream or a file: open a View on the Binary table, execute the View, fetch the Record, and then call one of the Record.GetStream() overloads. Then you'll need to pass this data to a deferred CA because an immediate CA should not modify system state and a deferred CA cannot read the MSI database. (And also because it needs to be after the InstallSqlData CA as mentioned above.) To pass that data, fill a CustomActionData object with the data and invoke the deferred CA with session.DoAction(deferredActionName, actionData). Then from within the deferred CA you can access that data as the session.CustomActionData property. Finally, don't forget about rollback and uninstall! 3. A DTF CA DLL is authored in WiX exactly like an unmanaged CA DLL. You need a Binary element for the DLL, a CustomAction element for each CA entrypoint, and a Custom Action=... to sequence each call in InstallExecuteSequence. When it comes to the MSI/WiX authoring, there are no additional elements you need to worry about just because the CA is managed or using DTF (other than perhaps a LaunchCondition to verify .NET is available). Hope this helps. -Jason- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Jim Sent: Friday, June 20, 2008 4:24 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] DTF custom action questions My installation creates and then interacts with a SQL Server database. Up until now, I've been able to do everything I need to do from WiX using the standard extensions, but now I'm facing a problem for which I need a custom action. I have to import some data into my database, but I need to modify it based on information gathered during the installation. Here are my questions: 1. How can I properly schedule my custom action to ensure it runs after my other SqlScripts and SqlStrings have been run? 2. How can I use data files (stored in the MSI with the Binary element*) in my custom action? I don't want to actually install them on the user's machine, just use them during the installation. 3. I'm having a hard time getting my head around how to correctly author and deploy a DTF custom action. Using Votive, I'm able to build the CA assemblies properly, but what do I need to add in my WiX project to make sure all of the elements are available to execute the custom action? DTF.chm has a good enough sample of C# code that I can follow the CA method creation, but can somebody point me to a sample fragment that includes all of the elements necessary to get a DTF CA to run? * I'm not wedded to using them as Binary streams in the MSI; if somebody has a better suggestion, please feel free to chime in. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source.
Re: [WiX-users] Separate ExitDialog for Uninstall
Apparently my response got lost in the mail, apologies if it is received twice. My response contains the solution. Troy -Original Message- From: Troy Simpson [mailto:[EMAIL PROTECTED] Sent: Saturday, 21 June 2008 9:00 AM To: 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] Separate ExitDialog for Uninstall I'm not sure how much research I would have needed to discover I did not add a 'hidden' attribute to the control. It was a bad assumption on my behalf that a condition to show does not imply an otherwise non-displaying state. The private property to use is: Condition Action=showWixUI_InstallMode = Remove/Condition The event may be to remove, however it is also setting properties. This allows us to tailor responses based upon the install or maintenance action. Troy -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 8:58 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall I will not do the research for you - the link I sent shows the difference between a public and a private property. In short public properties are also properties that are set as a result of user interaction. What you are doing is not setting a property, but an event which is called Remove as in: Control Id=Remove Type=PushButton X=236 Y=243 Width=56 Height=17 Text=[ButtonText_Remove] Default=yes Publish Event=Remove Value=ALL![CDATA[OutOfDiskSpace 1]]/Publish Try with REMOVE=ALL condition once more. Troy Simpson wrote: I think I see where this is going, but hopefully it might be more intuitive. I can set a property based on whether the product is already installed, but what I need to do is retrieve the property value when the remove button is clicked. Given that the property set by the remove button is private, is there a way of also setting a public property value? i.e., can multiple properties be set by one button press? Or is that off the mark? Thanks for the help so far, this seems like a fairly fundamental thing and is the last remaining issue in my installer. -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 7:58 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall There is a difference between REMOVE and Remove - the first one is a public property, the second is a private: http://msdn.microsoft.com/en-us/library/aa371245(VS.85).aspx I will let others to continue on this issue. Perhaps I will look at your project. Troy Simpson wrote: The Remove=All didn't work, I had tried variations of that previously. I looked at the Remove button on the maintenance dialog and the property that is being set is WixUI_InstallMode, and the value is Remove, so I tried the condition: Not WixUI_InstallMode=Remove That did not work either. I have tried many, many variations, and none have worked. I'm sure I'm doing something silly though. I have uploaded my wix build project to here: http://www.ebswift.com/temp/buildsubversion.zip It doesn't include any of the subversion binaries so it won't build, but the files are there. In the BuildSubversion\WixDialog folder you will see the PostDlg.wxs that I am trying to get the condition working in. -Original Message- From: [EMAIL PROTECTED] [mailto:wix-users- [EMAIL PROTECTED] On Behalf Of Calin Iaru Sent: Friday, 20 June 2008 6:43 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Separate ExitDialog for Uninstall EXISTINGPRODUCTS was a suggestion; what you need to do is to use a different property that when set, will show a different dialog control. For instance, if the user does an uninstall, use the REMOVE=ALL condition. Troy Simpson wrote: Thanks for the suggestions Calin, Preferably, I'd like to have the condition in the modified ExitDlg - I've made a copy of it and using that instead. The existingproducts condition did not seem to make any difference, the control code is as follows: Control Id=PostText Type=ScrollableText X=20 Y=70 Width=330 Height=151 Sunken=yes TabSkip=no Text SourceFile=!(wix.WixUIPostRtf=$(var.postRtf)) /Text Condition Action=showEXISTINGPRODUCTS/Condition /Control Is there anything jumping out there that can
