[WiX-users] Conditions for Install, Uninstall, Repair
I am using these conditions but they are behaving strangly: InstallExecuteSequence!--Set properties for Installation--Custom Action=CA_SetProperty_MACHINENAME After=CostFinalizeNOT Installed/CustomCustom Action=CA_SetProperty_SDK_MACHINE After=CA_SetProperty_MACHINENAMENOT Installed/Custom !--For Install Only--Custom Action=CA_SetBase_Install Before=CA_Install(NOT Installed) OR (UPGRADINGPRODUCTCODE) OR NOT(REMOVE = ALL)/CustomCustom Action=CA_Install After=CA_Rollback(NOT Installed) OR (UPGRADINGPRODUCTCODE) OR NOT(REMOVE = ALL) OR (Installed AND (InstallMode = Repair))/Custom !--For Repair Only (properties set during Uninstall are going to use here also)--Custom Action=CA_SetBase_Repair Before=CA_InstallInstalled AND (InstallMode = Repair)/Custom !--For Rollback Only--Custom Action=CA_SetBase_Rollback Before=CA_RollbackNOT Installed/CustomCustom Action=CA_Rollback After=StartServicesNOT Installed/Custom !--Set properties for Uninstall--Custom Action=CA_SetProperty_SDKMACHINE After=AppSearchInstalled/CustomCustom Action=CA_SetProperty_INSTALLPATH After=CA_SetProperty_SDKMACHINEInstalled/Custom !--For UnInstall Only--Custom Action=CA_SetBase_UnInstall Before=CA_UnInstallInstalled/CustomCustom Action=CA_UnInstall After=MsiUnpublishAssembliesInstalled AND ((NOT UPGRADINGPRODUCTCODE) AND (REMOVE = ALL)) AND (InstallMode = Remove)/Custom /InstallExecuteSequence On install, I am adding three registry values, but on repair first i read these values, run a custom action. But the last registry value gets deleted but other two remains the same. Ok registry values are populated during install and input are taken from textbox. But All registry addition are same but I am not sure why only last value gets removed? Can anyone please show me the error in the above code? or can some one show me condition which runs *only on* INSTALL, REPAIR, UNINSTALL and UPGRADE -- Thanks and Regards, Ravi Raj -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions for Install, Uninstall, Repair
I have checked that InstallMode = Repair or InstallMode = Remove is not working at all. On Thu, Jun 14, 2012 at 12:56 PM, Ravi Raj raviraj.callin...@gmail.comwrote: I am using these conditions but they are behaving strangly: InstallExecuteSequence!--Set properties for Installation--Custom Action=CA_SetProperty_MACHINENAME After=CostFinalizeNOT Installed/CustomCustom Action=CA_SetProperty_SDK_MACHINE After=CA_SetProperty_MACHINENAMENOT Installed/Custom !--For Install Only--Custom Action=CA_SetBase_Install Before=CA_Install(NOT Installed) OR (UPGRADINGPRODUCTCODE) OR NOT(REMOVE = ALL)/CustomCustom Action=CA_Install After=CA_Rollback(NOT Installed) OR (UPGRADINGPRODUCTCODE) OR NOT(REMOVE = ALL) OR (Installed AND (InstallMode = Repair))/Custom !--For Repair Only (properties set during Uninstall are going to use here also)--Custom Action=CA_SetBase_Repair Before=CA_InstallInstalled AND (InstallMode = Repair)/Custom !--For Rollback Only--Custom Action=CA_SetBase_Rollback Before=CA_RollbackNOT Installed/CustomCustom Action=CA_Rollback After=StartServicesNOT Installed/Custom !--Set properties for Uninstall--Custom Action=CA_SetProperty_SDKMACHINE After=AppSearchInstalled/CustomCustom Action=CA_SetProperty_INSTALLPATH After=CA_SetProperty_SDKMACHINEInstalled/Custom !--For UnInstall Only--Custom Action=CA_SetBase_UnInstall Before=CA_UnInstallInstalled/CustomCustom Action=CA_UnInstall After=MsiUnpublishAssembliesInstalled AND ((NOT UPGRADINGPRODUCTCODE) AND (REMOVE = ALL)) AND (InstallMode = Remove)/Custom /InstallExecuteSequence On install, I am adding three registry values, but on repair first i read these values, run a custom action. But the last registry value gets deleted but other two remains the same. Ok registry values are populated during install and input are taken from textbox. But All registry addition are same but I am not sure why only last value gets removed? Can anyone please show me the error in the above code? or can some one show me condition which runs *only on* INSTALL, REPAIR, UNINSTALL and UPGRADE -- Thanks and Regards, Ravi Raj -- Thanks and Regards, Ravi Raj -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions for Install, Uninstall, Repair
ok i got this Remove=ALL works great. On Thu, Jun 14, 2012 at 2:19 PM, Ravi Raj raviraj.callin...@gmail.comwrote: I have checked that InstallMode = Repair or InstallMode = Remove is not working at all. On Thu, Jun 14, 2012 at 12:56 PM, Ravi Raj raviraj.callin...@gmail.comwrote: I am using these conditions but they are behaving strangly: InstallExecuteSequence!--Set properties for Installation--Custom Action=CA_SetProperty_MACHINENAME After=CostFinalizeNOT Installed/CustomCustom Action=CA_SetProperty_SDK_MACHINE After=CA_SetProperty_MACHINENAMENOT Installed/Custom !--For Install Only--Custom Action=CA_SetBase_Install Before=CA_Install(NOT Installed) OR (UPGRADINGPRODUCTCODE) OR NOT(REMOVE = ALL)/CustomCustom Action=CA_Install After=CA_Rollback(NOT Installed) OR (UPGRADINGPRODUCTCODE) OR NOT(REMOVE = ALL) OR (Installed AND (InstallMode = Repair))/Custom !--For Repair Only (properties set during Uninstall are going to use here also)--Custom Action=CA_SetBase_Repair Before=CA_InstallInstalled AND (InstallMode = Repair)/Custom !--For Rollback Only--Custom Action=CA_SetBase_Rollback Before=CA_RollbackNOT Installed/CustomCustom Action=CA_Rollback After=StartServicesNOT Installed/Custom !--Set properties for Uninstall--Custom Action=CA_SetProperty_SDKMACHINE After=AppSearchInstalled/CustomCustom Action=CA_SetProperty_INSTALLPATH After=CA_SetProperty_SDKMACHINEInstalled/Custom !--For UnInstall Only--Custom Action=CA_SetBase_UnInstall Before=CA_UnInstallInstalled/CustomCustom Action=CA_UnInstall After=MsiUnpublishAssembliesInstalled AND ((NOT UPGRADINGPRODUCTCODE) AND (REMOVE = ALL)) AND (InstallMode = Remove)/Custom /InstallExecuteSequence On install, I am adding three registry values, but on repair first i read these values, run a custom action. But the last registry value gets deleted but other two remains the same. Ok registry values are populated during install and input are taken from textbox. But All registry addition are same but I am not sure why only last value gets removed? Can anyone please show me the error in the above code? or can some one show me condition which runs *only on* INSTALL, REPAIR, UNINSTALL and UPGRADE -- Thanks and Regards, Ravi Raj -- Thanks and Regards, Ravi Raj -- Thanks and Regards, Ravi Raj -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditions on a Fragment
Hello, I have a number of fragments say A, B C. What I would like to do is to install fragment A if the the OS is Windows 7, install fragment B if the OS is Win XP and install fragent C if its Windows Vista. So its a selective install of fragments based on OS. I thought of using a condition element but I don't think that would be appropriate (as far as I understand it would throw up a message to user which is not what I want.). Any help on this would be greatly appreciated. Thank you, Anil. -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions on a Fragment
Fragments are a compiler/build concept not an installer/runtime concept. Take a look at component conditions ( Condition element nested under a Component element ) and the VersionNT property. From: Anil Patel apatel...@googlemail.com Sent: Monday, September 05, 2011 9:29 AM To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Subject: [WiX-users] Conditions on a Fragment Hello, I have a number of fragments say A, B C. What I would like to do is to install fragment A if the the OS is Windows 7, install fragment B if the OS is Win XP and install fragent C if its Windows Vista. So its a selective install of fragments based on OS. I thought of using a condition element but I don't think that would be appropriate (as far as I understand it would throw up a message to user which is not what I want.). Any help on this would be greatly appreciated. Thank you, Anil. -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions on a Fragment
Thanks Christopher. I'll look at component conditions. Regards, Anil. On Mon, Sep 5, 2011 at 3:46 PM, Christopher Painter chr...@deploymentengineering.com wrote: Fragments are a compiler/build concept not an installer/runtime concept. Take a look at component conditions ( Condition element nested under a Component element ) and the VersionNT property. From: Anil Patel apatel...@googlemail.com Sent: Monday, September 05, 2011 9:29 AM To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Subject: [WiX-users] Conditions on a Fragment Hello, I have a number of fragments say A, B C. What I would like to do is to install fragment A if the the OS is Windows 7, install fragment B if the OS is Win XP and install fragent C if its Windows Vista. So its a selective install of fragments based on OS. I thought of using a condition element but I don't think that would be appropriate (as far as I understand it would throw up a message to user which is not what I want.). Any help on this would be greatly appreciated. Thank you, Anil. -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions not working at all
On 30-Jul-11 10:07, Marc Bauer wrote: Condition Message=Previous version of MyApp installed.UNINSTALLNSIS AND NOT Installed/Condition Launch conditions indicate the condition that are required for install to proceed; if the condition isn't met, the install is canceled with the specified message. Your condition is being met, so there's no error. -- sig://boB http://joyofsetup.com/ -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditions not working at all
Hi I'm trying to uninstall an old app that was made with suxxx NSIS installer and need to upgrade it to MSI. What could be the best way? I tried to make a registry search and set the UNINSTALLNSIS property. I ran MSI with debug mode and see the property has been set: MSI (c) (78:40) [15:40:42:577]: PROPERTY CHANGE: Adding UNINSTALLNSIS property. Its value is 'C:\Program Files (x86)\MyApp\uninstall.exe'. But the Condition Message I have added for debugging does not popup. I tried UNINSTALLNSIS and UNINSTALLNSIS AND NOT Installed both no success. This should only be evaluated on install as a side note. Property Id=UNINSTALLNSIS RegistrySearch Id=UNINSTALLNSIS_REGSEARCH Root=HKLM Key=SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\MyApp Name=UninstallString Type=raw / /Property Condition Message=Previous version of MyApp installed.UNINSTALLNSIS AND NOT Installed/Condition Here is the full example about what I planed to do: Property Id=UNINSTALLNSIS RegistrySearch Id=UNINSTALLNSIS_REGSEARCH Root=HKLM Key=SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\MyApp Name=UninstallString Type=raw / /Property Property Id=QtExecCmdLine Value=UNINSTALLNSIS /S/ CustomAction Id=QtMyAppUninstallWithNSIS BinaryKey=WixCA DllEntry=CAQuietExec Execute=immediate Return=check/ InstallExecuteSequence Custom Action=QtMyAppUninstallWithNSIS After=InstallInitialize/ /InstallExecuteSequence I also need to run RemoveFolderEx somewhere directly after the silent uninstall custom action as these NSIS uninstall is *very* buggy... many stale files in there. Any chance to get this RemoveFolderEx executed only if the app is removed with NSIS silent setup so I do not need to run RemoveFolderEx On=install? A newbie example would be of great help. This has been tested on WiX 3.6.1922. Regards Marc -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditions on DialogPublish//Dialog - how do I make it dependent on a Feature
Hi, I am attempting to customise my installer dialogs. I have a Dialog Id=SqlSpecDlg that prompts for a database instance name - but I only want to display the Dialog if the user has opted to install Feature Id=DbFeature On the previous Dialog I have this: Publish Dialog=CustomizeDlg Control=Next Event=NewDialog Value=SqlSpecDlg Order=1[CDATA[(DbFeature=3)]]/Publish This is giving an error: Entity 'DbFeature' not defined. Feature Id=DbFeature is defined in a different file although I tried moving all the code into the same file and got the same error. Can someone guess as to what is wrong here? Is the syntax of my condition incorrect? thanks in advance JamieT -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions on DialogPublish//Dialog - how do Imake it dependent on a Feature
Sorry, please ignore. I was making this much more difficult than it had to be. This seems to be what I want: Publish Dialog=CustomizeDlg Control=Next Event=NewDialog Value=SqlSpecDlg Order=1DbFeature=3/Publish Hopefully will help someone who might one day search for this anyway!!! JamieT -Original Message- From: Jamie Thomson Sent: Friday, February 11, 2011 5:15 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Conditions on - how do Imake it dependent on a Hi, I am attempting to customise my installer dialogs. I have a Dialog Id=SqlSpecDlg that prompts for a database instance name - but I only want to display the Dialog if the user has opted to install Feature Id=DbFeature On the previous Dialog I have this: Publish Dialog=CustomizeDlg Control=Next Event=NewDialog Value=SqlSpecDlg Order=1[CDATA[(DbFeature=3)]]/Publish This is giving an error: Entity 'DbFeature' not defined. Feature Id=DbFeature is defined in a different file although I tried moving all the code into the same file and got the same error. Can someone guess as to what is wrong here? Is the syntax of my condition incorrect? thanks in advance JamieT -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions for Uninstall/Remove Only
Hi, Yes, I used that too, but, at least in my case, the quotes didn't work, so I had to use it like this: Condition(NOT UPGRADINGPRODUCTCODE) AND (REMOVE=ALL)/Condition Viv On 4/1/2010 9:49 PM, little.forest wrote: Thanks Sanjay. This is great. Especially there is a table - much clearer. From: Sanjay Raos...@noida.interrasystems.com To: General discussion for Windows Installer XML toolset.wix-users@lists.sourceforge.net Sent: Wed, March 31, 2010 11:02:18 PM Subject: Re: [WiX-users] Conditions for Uninstall/Remove Only try out this one. (NOT UPGRADINGPRODUCTCODE) AND (REMOVE=ALL) for more details u can see http://stackoverflow.com/questions/320921/how-to-add-a-wix-custom-action-that-happens-only-on-uninstall-via-msi -Sanjay little.forest wrote: How can I create conditions for a custom action to run for Uninstall/Remove only? If I use condition 'Installed' then the CA runs in Repair mode. If I use condition 'Remove=ALL' then the CA doesn't run in Repair, but it doesn't run in Uninstall/Remove either. Thanks. __ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com. -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions for Uninstall/Remove Only
try out this one. (NOT UPGRADINGPRODUCTCODE) AND (REMOVE=ALL) for more details u can see http://stackoverflow.com/questions/320921/how-to-add-a-wix-custom-action-that-happens-only-on-uninstall-via-msi -Sanjay little.forest wrote: How can I create conditions for a custom action to run for Uninstall/Remove only? If I use condition 'Installed' then the CA runs in Repair mode. If I use condition 'Remove=ALL' then the CA doesn't run in Repair, but it doesn't run in Uninstall/Remove either. Thanks. __ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions for Uninstall/Remove Only
Thanks Sanjay. This is great. Especially there is a table - much clearer. From: Sanjay Rao s...@noida.interrasystems.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, March 31, 2010 11:02:18 PM Subject: Re: [WiX-users] Conditions for Uninstall/Remove Only try out this one. (NOT UPGRADINGPRODUCTCODE) AND (REMOVE=ALL) for more details u can see http://stackoverflow.com/questions/320921/how-to-add-a-wix-custom-action-that-happens-only-on-uninstall-via-msi -Sanjay little.forest wrote: How can I create conditions for a custom action to run for Uninstall/Remove only? If I use condition 'Installed' then the CA runs in Repair mode. If I use condition 'Remove=ALL' then the CA doesn't run in Repair, but it doesn't run in Uninstall/Remove either. Thanks. __ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com. -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditions for Uninstall/Remove Only
How can I create conditions for a custom action to run for Uninstall/Remove only? If I use condition 'Installed' then the CA runs in Repair mode. If I use condition 'Remove=ALL' then the CA doesn't run in Repair, but it doesn't run in Uninstall/Remove either. Thanks. __ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions for Uninstall/Remove Only
That's because property names are case sensitive and the actual name is REMOVE. Phil Wilson -Original Message- From: little.forest [mailto:little.for...@ymail.com] Sent: Wednesday, March 31, 2010 3:55 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditions for Uninstall/Remove Only How can I create conditions for a custom action to run for Uninstall/Remove only? If I use condition 'Installed' then the CA runs in Repair mode. If I use condition 'Remove=ALL' then the CA doesn't run in Repair, but it doesn't run in Uninstall/Remove either. Thanks. __ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com. -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ 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). -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions for Uninstall/Remove Only
Thanks Phil! That works. Sorry, I didn't pay attention on that. From: Wilson, Phil phil.wil...@invensys.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wed, March 31, 2010 4:17:59 PM Subject: Re: [WiX-users] Conditions for Uninstall/Remove Only That's because property names are case sensitive and the actual name is REMOVE. Phil Wilson -Original Message- From: little.forest [mailto:little.for...@ymail.com] Sent: Wednesday, March 31, 2010 3:55 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditions for Uninstall/Remove Only How can I create conditions for a custom action to run for Uninstall/Remove only? If I use condition 'Installed' then the CA runs in Repair mode. If I use condition 'Remove=ALL' then the CA doesn't run in Repair, but it doesn't run in Uninstall/Remove either. Thanks. __ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now http://ca.toolbar.yahoo.com. -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ 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). -- Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __ Get a sneak peak at messages with a handy reading pane with All new Yahoo! Mail: http://ca.promos.yahoo.com/newmail/overview2/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] conditions
Hi,
I am tyring to use a condition to check if a pre-requisite application is
installed. The way I am doing it is to set a property with a registry search.
I am checking this preperty in a condition, nd want the installation to stop if
the registry is not found, and display a message to the user.
The problem I am getting is that when I try to compile, I get the error message
that the condition element contains an unexpected attribute 'Message'. Where
can I put the message?
Here is the code:
Component Id='CheckAX' Guid='{ACC8C0B1-B59F-49d2-99F2-7B7F7702C7A8}'
Condition Message='This application requires Microsoft Dynamics Business
Connector to be installed. Please install then run setup again.'
![CDATA[Installed OR BUSINESSCONNECTOR]]
/Condition
/Component
Feature Id=ProductFeature Title=NeuScanSetup Level=1
ComponentRef Id=CheckAX /
/Feature
Thanks.
_
We want to hear all your funny, exciting and crazy Hotmail stories. Tell us now
http://clk.atdmt.com/UKM/go/195013117/direct/01/
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] conditions
Hi,
You are trying to create Launch Condition and refer to Wix documentation
to create Launch Condition you Condition element should be child node
under Product or Fragment element, so you simply need to remove
Component above your Condition.
Igor
-Original Message-
From: Shabbir Ahsan [mailto:shabbir_ah...@hotmail.com]
Sent: Tuesday, March 09, 2010 11:03 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] conditions
Hi,
I am tyring to use a condition to check if a pre-requisite application
is installed. The way I am doing it is to set a property with a
registry search. I am checking this preperty in a condition, nd want
the installation to stop if the registry is not found, and display a
message to the user.
The problem I am getting is that when I try to compile, I get the error
message that the condition element contains an unexpected attribute
'Message'. Where can I put the message?
Here is the code:
Component Id='CheckAX' Guid='{ACC8C0B1-B59F-49d2-99F2-7B7F7702C7A8}'
Condition Message='This application requires Microsoft Dynamics
Business Connector to be installed. Please install then run setup
again.'
![CDATA[Installed OR BUSINESSCONNECTOR]]
/Condition
/Component
Feature Id=ProductFeature Title=NeuScanSetup Level=1
ComponentRef Id=CheckAX /
/Feature
Thanks.
_
We want to hear all your funny, exciting and crazy Hotmail stories. Tell
us now
http://clk.atdmt.com/UKM/go/195013117/direct/01/
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
/pre
BR style=font-size:4px;
a href = http://www.sdl.com;img src=http://www.sdl.com/images/email
logo_150dpi-01.png alt=www.sdl.com border=0//a
BR
font face=arial size=2 a href = http://www.sdl.com;
style=color:005740; font-weight: boldwww.sdl.com/a
BR
BR
font face=arial size=1 color=#736F6E
bSDL PLC confidential, all rights reserved./b
If you are not the intended recipient of this mail SDL requests and requires
that you delete it without acting upon or copying any of its contents, and we
further request that you advise us.BR
SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.BR
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY,
UK.
/font
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Re [WIX-users] conditions
Hi Igor, thanks. Moving the condition out of component and just under package sorted it!! _ Got a cool Hotmail story? Tell us now http://clk.atdmt.com/UKM/go/195013117/direct/01/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions with properties through UI
Jeffrey Bindinga wrote: In the logfile I see that the property is set on the UI and the INSTALL (no typo's either), but my condition still evaluates to false while DEPLOYMENTTYPE is AllInOne. See http://www.joyofsetup.com/2007/05/30/feature-conditions-and-ui/. -- sig://boB http://joyofsetup.com/ -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditions with properties through UI
Hi All, I've got a problem with my condition using a property. I set this property in the UI with my own dialog buttons which have the following code. !--The DEPLOYMENTTYPE buttons-- Control Id=AllInOne Type=PushButton Height=41 Width=41 X=72 Y=80 Bitmap=yes Text=AllInOneImg Publish Property=DEPLOYMENTTYPE Value=AllInOne1/Publish /Control Control Id=DedicatedServer Type=PushButton Height=41 Width=41 X=72 Y=155 Bitmap=yes Text=DedicatedServerImg Publish Property=DEPLOYMENTTYPE Value=DedicatedServer1/Publish /Control On the fragment of the feature I set the property to a default: Property Id=DEPLOYMENTTYPE Value=DedicatedServer Secure=yes/ On my feature I have the following condition: Condition Level=1![CDATA[DEPLOYMENTTYPE = AllInOne) OR Installed]]/Condition In the logfile I see that the property is set on the UI and the INSTALL (no typo's either), but my condition still evaluates to false while DEPLOYMENTTYPE is AllInOne. What am I doing wrong here? Regards, Jeffrey Bindinga -- View this message in context: http://n2.nabble.com/Conditions-with-properties-through-UI-tp4144437p4144437.html Sent from the wix-users mailing list archive at Nabble.com. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditions in merge modules
I'm creating a merge module for inclusion in another company's msi package. It does not appear to be possible to put conditions (such as checking operating system version or .net installed version) in the merge module. How is that generally handled? Thanks. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions in merge modules
Are you talking about LaunchConditions, Feature conditions, or Component conditions? You can't isolate your merge module parts in a final MSI very easily, but you should be able to condition any/all of your components and/or custom actions your merge module contributes. -Original Message- From: Ken Halprin [mailto:khalp...@autosoln.com] Sent: Wednesday, December 09, 2009 10:08 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditions in merge modules I'm creating a merge module for inclusion in another company's msi package. It does not appear to be possible to put conditions (such as checking operating system version or .net installed version) in the merge module. How is that generally handled? Thanks. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions in merge modules
To get a feel for how wix works, I created an installer project which produces an .msi file. It includes conditions at the Product level (are those launch conditions?) that check for os version and .net version, exiting the install if the condition is not met. I'll convert that project into a merge module project and would like to do the same checks. Would I need to put the condition checks on each feature to be installed? -Original Message- From: Blair [mailto:os...@live.com] Sent: Wednesday, December 09, 2009 12:38 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Conditions in merge modules Are you talking about LaunchConditions, Feature conditions, or Component conditions? You can't isolate your merge module parts in a final MSI very easily, but you should be able to condition any/all of your components and/or custom actions your merge module contributes. -Original Message- From: Ken Halprin [mailto:khalp...@autosoln.com] Sent: Wednesday, December 09, 2009 10:08 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditions in merge modules I'm creating a merge module for inclusion in another company's msi package. It does not appear to be possible to put conditions (such as checking operating system version or .net installed version) in the merge module. How is that generally handled? Thanks. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions in merge modules
WiX exposes (for the most part) all of the power of native Windows Installer. LaunchConditions are exposed by the Condition elements under the Product and Fragment elements and result in entries into the LaunchCondition table (http://msdn.microsoft.com/library/aa369752.aspx) which is processed by the built-in LaunchConditions action (http://msdn.microsoft.com/library/aa369751.aspx). According to http://msdn.microsoft.com/library/aa369823.aspx merge modules can't supply LaunchCondition table rows. However, they can supply what are known as Type 19 custom actions. In WiX, type 19 custom actions are created by supplying the Id and Error attribute values to the CustomAction element, and then scheduling that action with one or two instances (usually two, one under the InstallIUSequence element and the other under the InstallExecuteSequence element) of the Custom element. -Original Message- From: Ken Halprin [mailto:khalp...@autosoln.com] Sent: Wednesday, December 09, 2009 11:58 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Conditions in merge modules To get a feel for how wix works, I created an installer project which produces an .msi file. It includes conditions at the Product level (are those launch conditions?) that check for os version and .net version, exiting the install if the condition is not met. I'll convert that project into a merge module project and would like to do the same checks. Would I need to put the condition checks on each feature to be installed? -Original Message- From: Blair [mailto:os...@live.com] Sent: Wednesday, December 09, 2009 12:38 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Conditions in merge modules Are you talking about LaunchConditions, Feature conditions, or Component conditions? You can't isolate your merge module parts in a final MSI very easily, but you should be able to condition any/all of your components and/or custom actions your merge module contributes. -Original Message- From: Ken Halprin [mailto:khalp...@autosoln.com] Sent: Wednesday, December 09, 2009 10:08 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditions in merge modules I'm creating a merge module for inclusion in another company's msi package. It does not appear to be possible to put conditions (such as checking operating system version or .net installed version) in the merge module. How is that generally handled? Thanks. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditions issue
Moderate time user, first time question asker. I'm having issues where my protection condition around a component that includes an inifile is not working correctly, yet when I include the value of the tested variable it appears like it should be Sample Property Id='OSINSTALLDIR' Secure='yes' Value='C:\Program Files\'/ Property Id='CONFIGINIEXISTS' DirectorySearch Id='ConfigDirectorySearch' Path='[OSINSTALLDIR]Static\Path\' Depth='0' FileSearch Id='CheckIniFile' Name='config.ini'/ /DirectorySearch /Property And later Component Id='ConfigIniComponent' Guid='1fdcfd16-db4c-4de3-b06e-12f6d2f4c270' SharedDllRefCount='yes' IniFile Id='WriteConnectionStringRobotics' Action='addLine' Key='Connect0' Directory='ConfigLocation' Name='Config.ini' Section='Robotic Connections' Value='Provider=SQLOLEDB.1;Integrated Security = SSPI;Initial Catalog=[DATABASENAME];Data Source=[DATABASESERVER];'/ IniFile Id='WriteEnvironmentMain' Action='addLine' Key='Environment' Directory=' ConfigLocation' Name='Config.ini' Section='Main' Value='0'/ IniFile Id='WriteConnectionStringMain' Action='addLine' Key='Connect0' Directory=' ConfigLocation' Name='Config.ini' Section='Main' Value='Provider=SQLOLEDB.1;Integrated Security = SSPI;Initial Catalog=[DATABASENAME];Data Source=[DATABASESERVER];'/ IniFile Id='CaereLicenseIni' Action='addLine' Key='License File' Directory=' ConfigLocation' Value='[RedCap05]oscaere.lic' Name='Config.ini' Section='Caere License' / IniFile Id='tempwrite' Action='addLine' Key='templine' Directory=' ConfigLocation' Value='[OSINSTALLDIR]Static\Path' Name='Config.ini' Section='temp'/ IniFile Id='output' Action='addLine' Key='newline' Directory=' ConfigLocation' Value='[CONFIGINIEXISTS]' Name='Config.ini' Section='temp'/ Condition ![CDATA[NOT CONFIGINIEXISTS]]/Condition /Component I've tried with and without the CDATA wrapping CONFIGINIEXISTS and it isn't wanting to work either way. And the output line I'm writing to configini (when I've already got the file there) is filled in with the path and file name. I've researched but this looks like it should work. I figure I'm doing something simple and dumb. I've tried pre-setting OSINSTALLDIR inside the installer AND in my batch file I'm calling the MSI from via the command line. Any info I'm missing that will help just point out and I'll supply it. Thanks ~Patrick Sullivan -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions issue
Does a verbose log file show the Property getting set? Patrick Sullivan wrote: Moderate time user, first time question asker. I'm having issues where my protection condition around a component that includes an inifile is not working correctly, yet when I include the value of the tested variable it appears like it should be Sample Property Id='OSINSTALLDIR' Secure='yes' Value='C:\Program Files\'/ Property Id='CONFIGINIEXISTS' DirectorySearch Id='ConfigDirectorySearch' Path='[OSINSTALLDIR]Static\Path\' Depth='0' FileSearch Id='CheckIniFile' Name='config.ini'/ /DirectorySearch /Property And later Component Id='ConfigIniComponent' Guid='1fdcfd16-db4c-4de3-b06e-12f6d2f4c270' SharedDllRefCount='yes' IniFile Id='WriteConnectionStringRobotics' Action='addLine' Key='Connect0' Directory='ConfigLocation' Name='Config.ini' Section='Robotic Connections' Value='Provider=SQLOLEDB.1;Integrated Security = SSPI;Initial Catalog=[DATABASENAME];Data Source=[DATABASESERVER];'/ IniFile Id='WriteEnvironmentMain' Action='addLine' Key='Environment' Directory=' ConfigLocation' Name='Config.ini' Section='Main' Value='0'/ IniFile Id='WriteConnectionStringMain' Action='addLine' Key='Connect0' Directory=' ConfigLocation' Name='Config.ini' Section='Main' Value='Provider=SQLOLEDB.1;Integrated Security = SSPI;Initial Catalog=[DATABASENAME];Data Source=[DATABASESERVER];'/ IniFile Id='CaereLicenseIni' Action='addLine' Key='License File' Directory=' ConfigLocation' Value='[RedCap05]oscaere.lic' Name='Config.ini' Section='Caere License' / IniFile Id='tempwrite' Action='addLine' Key='templine' Directory=' ConfigLocation' Value='[OSINSTALLDIR]Static\Path' Name='Config.ini' Section='temp'/ IniFile Id='output' Action='addLine' Key='newline' Directory=' ConfigLocation' Value='[CONFIGINIEXISTS]' Name='Config.ini' Section='temp'/ Condition ![CDATA[NOT CONFIGINIEXISTS]]/Condition /Component I've tried with and without the CDATA wrapping CONFIGINIEXISTS and it isn't wanting to work either way. And the output line I'm writing to configini (when I've already got the file there) is filled in with the path and file name. I've researched but this looks like it should work. I figure I'm doing something simple and dumb. I've tried pre-setting OSINSTALLDIR inside the installer AND in my batch file I'm calling the MSI from via the command line. Any info I'm missing that will help just point out and I'll supply it. Thanks ~Patrick Sullivan -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions with util:XMLConfig
Again, I found my solution by myself: To define custom conditions for the SchedXmlConfig action that gets added when you use XMLConfig, you simply have to reschedule it in the installExecuteSequence and there, you will be able to set your own conditions. For instance: InstallExecuteSequence Custom Action=SchedXmlConfig After=DuplicateFilesVersionNT gt; 400 AND MyProperty lt; 1)/Custom /InstallExecuteSequence Hope this could help others... De : Routhier Louis Envoyé : jeudi 21 mai 2009 10:46 À : 'wix-users@lists.sourceforge.net' Objet : Conditions with util:XMLConfig When using XMLConfig from UtilExtension, a SchedXmlConfig entry is created in the InstallExecuteSequence table with condition set to VersionNT 400. Is there any way of specifying additional conditions? I would need a way to allow users to select if they want to remove the config or not since it may be shared with other installations. BTW, is there any way of searching in the mailing list archive? I've only found a place to browse them... Thank you! Les renseignements contenus dans ce message peuvent être confidentiels. Si vous n'êtes pas le destinataire visé ou une personne autorisée à lui remettre ce courriel, vous êtes par la présente avisé qu'il est strictement interdit d'utiliser, de copier ou de distribuer ce courriel, de dévoiler la teneur de ce message ou de prendre quelque mesure fondée sur l'information contenue. Vous êtes donc prié d'aviser immédiatement l'expéditeur de cette erreur et de détruire ce message sans garder de copie. -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, Big Spaceship. http://www.creativitycat.com ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditions with util:XMLConfig
When using XMLConfig from UtilExtension, a SchedXmlConfig entry is created in the InstallExecuteSequence table with condition set to VersionNT 400. Is there any way of specifying additional conditions? I would need a way to allow users to select if they want to remove the config or not since it may be shared with other installations. BTW, is there any way of searching in the mailing list archive? I've only found a place to browse them... Thank you! Les renseignements contenus dans ce message peuvent être confidentiels. Si vous n'êtes pas le destinataire visé ou une personne autorisée à lui remettre ce courriel, vous êtes par la présente avisé qu'il est strictement interdit d'utiliser, de copier ou de distribuer ce courriel, de dévoiler la teneur de ce message ou de prendre quelque mesure fondée sur l'information contenue. Vous êtes donc prié d'aviser immédiatement l'expéditeur de cette erreur et de détruire ce message sans garder de copie. -- Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, Big Spaceship. http://www.creativitycat.com ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditions based on XML Search
I see there is a RegistrySearch, FileSearch, DirectorySearch, AppSearch .. and even an IniFileSearch. Is there such a thing as XMLFileSearch? I'd like to do some conditional processing based on XML. Any solutions out there? - Troy -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions based on XML Search
troy hostetter wrote: I see there is a RegistrySearch, FileSearch, DirectorySearch, AppSearch .. and even an IniFileSearch. Is there such a thing as XMLFileSearch? Not in WiX today. -- sig://boB http://joyofsetup.com/ -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions in fragments
You can also have an empty component group and add reference to it from the product file. - this is what I do :^) -Original Message- From: Frederico Rico Apostolo [mailto:frederico.apost...@vantyx.com] Sent: Friday, February 20, 2009 4:49 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Conditions in fragments I'm using v3 votive in vs2005 and I lost sometime trying to have a fragment with only launch conditions, I've realized that even with compile propriety in the solution that fragment was ignored, unless I had a propriety or a custom action in that fragment linked or sub linked to the product, just a warning for those that try to be as modular as I , if I'm wrong correct me pls. __ Esta mensagem e ficheiros anexos incluem materia privada, confidencial e legalmente protegida, exclusivamente destinada a quem nela conste como destinatario. Se recebeu esta mensagem por engano, agradecemos que informe de imediato o remetente e que elimine a mensagem e os ficheiros sem os utilizar, divulgar ou reproduzir. This message and attached files contain private, confidential and legally privileged information, exclusively intended for the named addressees. If you have received this message in error, please contact the sender immediately and delete the message and files without utilization, circulation or reproduction. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions in fragments
You're right. Conditions are one thing that don't have a good way to reference. Maybe put the Properties referenced by the Conditions in the same Fragment, then use a PropertyRef? Frederico Rico Apostolo wrote: I'm using v3 votive in vs2005 and I lost sometime trying to have a fragment with only launch conditions, I've realized that even with compile propriety in the solution that fragment was ignored, unless I had a propriety or a custom action in that fragment linked or sub linked to the product, just a warning for those that try to be as modular as I , if I'm wrong correct me pls. __ Esta mensagem e ficheiros anexos incluem materia privada, confidencial e legalmente protegida, exclusivamente destinada a quem nela conste como destinatario. Se recebeu esta mensagem por engano, agradecemos que informe de imediato o remetente e que elimine a mensagem e os ficheiros sem os utilizar, divulgar ou reproduzir. This message and attached files contain private, confidential and legally privileged information, exclusively intended for the named addressees. If you have received this message in error, please contact the sender immediately and delete the message and files without utilization, circulation or reproduction. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions in fragments
Ick. smile/ Eitan Behar wrote: You can also have an empty component group and add reference to it from the product file. - this is what I do :^) -Original Message- From: Frederico Rico Apostolo [mailto:frederico.apost...@vantyx.com] Sent: Friday, February 20, 2009 4:49 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Conditions in fragments I'm using v3 votive in vs2005 and I lost sometime trying to have a fragment with only launch conditions, I've realized that even with compile propriety in the solution that fragment was ignored, unless I had a propriety or a custom action in that fragment linked or sub linked to the product, just a warning for those that try to be as modular as I , if I'm wrong correct me pls. __ Esta mensagem e ficheiros anexos incluem materia privada, confidencial e legalmente protegida, exclusivamente destinada a quem nela conste como destinatario. Se recebeu esta mensagem por engano, agradecemos que informe de imediato o remetente e que elimine a mensagem e os ficheiros sem os utilizar, divulgar ou reproduzir. This message and attached files contain private, confidential and legally privileged information, exclusively intended for the named addressees. If you have received this message in error, please contact the sender immediately and delete the message and files without utilization, circulation or reproduction. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditions
I'm try to check the file version of a required library as part of condition. I have code that looks like: Property Id=AProduct RegistrySearch Id='AProduct.Registry' Type='raw' Root='HKLM' Key='SOFTWARE\SomeCompany\SomeProduct' Name='CurrentVersion' / /Property Condition Message=This program requires SomeProduct AProduct /Condition Condition Message=This program requires version 1.6 or above of SomeProduct AProduct = 1.6 /Condition My first condition works ok (ie: the installation fails if the required product is not installed) but my second condition (which checks the version) doesn't fail when I expect it to. What am I doing wrong??? - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions
Craig Ward wrote: Condition Message=This program requires version 1.6 or above of SomeProduct AProduct = 1.6 /Condition The MSI doc says floating point numeric values are not supported. The general approach MSI offers for version comparisons is via AppSearch. In WiX, you could use RegistrySearch to get the path and FileSearch to confirm its version. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions for setup in GUI and without GUI?
Hi, Thank you for your hints, but this just doesn't work correctly. I do not need to create custom errors, if Condition statements do the same. So the helpful thoughts are in the lower part of your mail. That however does not work. If I set the UI_RAN property, the condition only fails if the NOT_WANTED_CONDITION fails. If the UI_RAN property is not set, it will fail anyhow, regardless of the NOT_WANTED_CONDITION. I tried the following: InstallExecuteSequence LaunchConditions Suppress='yes'NOT GUI/LaunchConditions /InstallExecuteSequence But that did'nt work either, since the condition NOT GUI seems to be simply ignored. Oliver Friedrich -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: Dienstag, 26. Juni 2007 17:17 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] [wix-users] Conditions for setup in GUI and without GUI? Yuo could create custom errors like this: Error Id=2000This is my error message/Error and create a custom action to trigger it like this: CustomAction Id=MyError Error=2000 / You can call this in the InstallExecuteSequence like this: Custom Action=MyErrorNOT WANTED_CONDITION /Custom The additional problem is how do you stop them triggering if the UI ran? You can create another CA like this: CustomAction Id=setUI_RAN Property=UI_RAN Value=1 / and schedule it at some point in the InstallUISequence (as long as it's before ExecuteAction). There's no need to declare the UI_RAN property; it will be created when the CA is run. The condition on your CA would then be something like: Custom Action=MyErrorNOT WANTED_CONDITION AND NOT UI_RAN/Custom Rob - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions for setup in GUI and without GUI?
You've set suppress=yes, which means the event doesn't occur. Rob Mailinglist wrote: Hi, Thank you for your hints, but this just doesn't work correctly. I do not need to create custom errors, if Condition statements do the same. So the helpful thoughts are in the lower part of your mail. That however does not work. If I set the UI_RAN property, the condition only fails if the NOT_WANTED_CONDITION fails. If the UI_RAN property is not set, it will fail anyhow, regardless of the NOT_WANTED_CONDITION. I tried the following: InstallExecuteSequence LaunchConditions Suppress='yes'NOT GUI/LaunchConditions /InstallExecuteSequence But that did’nt work either, since the condition “NOT GUI” seems to be simply ignored. Oliver Friedrich -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: Dienstag, 26. Juni 2007 17:17 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] [wix-users] Conditions for setup in GUI and without GUI? Yuo could create custom errors like this: Error Id=2000This is my error message/Error and create a custom action to trigger it like this: CustomAction Id=MyError Error=2000 / You can call this in the InstallExecuteSequence like this: Custom Action=MyErrorNOT WANTED_CONDITION /Custom The additional problem is how do you stop them triggering if the UI ran? You can create another CA like this: CustomAction Id=setUI_RAN Property=UI_RAN Value=1 / and schedule it at some point in the InstallUISequence (as long as it's before ExecuteAction). There's no need to declare the UI_RAN property; it will be created when the CA is run. The condition on your CA would then be something like: Custom Action=MyErrorNOT WANTED_CONDITION AND NOT UI_RAN/Custom Rob - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions for setup in GUI and without GUI?
Hi Rob, You've set suppress=yes, which means the event doesn't occur. Last compile I tried the following: InstallExecuteSequence LaunchConditions Suppress='no'NOT (GUI=1)/LaunchConditions /InstallExecuteSequence And it did not work either, it fails with the specified message of the condition. Maybe it is a bug? Oliver Friedrich Consultant - Software Solutions -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: Mittwoch, 27. Juni 2007 12:59 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Conditions for setup in GUI and without GUI? You've set suppress=yes, which means the event doesn't occur. Rob Mailinglist wrote: Hi, Thank you for your hints, but this just doesn't work correctly. I do not need to create custom errors, if Condition statements do the same. So the helpful thoughts are in the lower part of your mail. That however does not work. If I set the UI_RAN property, the condition only fails if the NOT_WANTED_CONDITION fails. If the UI_RAN property is not set, it will fail anyhow, regardless of the NOT_WANTED_CONDITION. I tried the following: InstallExecuteSequence LaunchConditions Suppress='yes'NOT GUI/LaunchConditions /InstallExecuteSequence But that did'nt work either, since the condition NOT GUI seems to be simply ignored. Oliver Friedrich -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: Dienstag, 26. Juni 2007 17:17 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] [wix-users] Conditions for setup in GUI and without GUI? Yuo could create custom errors like this: Error Id=2000This is my error message/Error and create a custom action to trigger it like this: CustomAction Id=MyError Error=2000 / You can call this in the InstallExecuteSequence like this: Custom Action=MyErrorNOT WANTED_CONDITION /Custom The additional problem is how do you stop them triggering if the UI ran? You can create another CA like this: CustomAction Id=setUI_RAN Property=UI_RAN Value=1 / and schedule it at some point in the InstallUISequence (as long as it's before ExecuteAction). There's no need to declare the UI_RAN property; it will be created when the CA is run. The condition on your CA would then be something like: Custom Action=MyErrorNOT WANTED_CONDITION AND NOT UI_RAN/Custom Rob - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions for setup in GUI and without GUI?
Hi Wix-users, Solved the problem, easier than thought. To disable LaunchConditions in UI Mode simply add the following: InstallUISequence LaunchConditions Suppress='yes'/ /InstallUISequence Important, must be in InstallUISequence so that the LaunchConditions are run if the msi is executed quiet. Thx for all hints. Oliver Friedrich - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions for setup in GUI and without GUI?
Just a sanity check. In your last message you said you were setting a UI_RAN property, but in your examples you're checking against a GUI property. You are setting and using the same property, right? Rob Mailinglist wrote: Hi Rob, You've set suppress=yes, which means the event doesn't occur. Last compile I tried the following: InstallExecuteSequence LaunchConditions Suppress='no'NOT (GUI=1)/LaunchConditions /InstallExecuteSequence And it did not work either, it fails with the specified message of the condition. Maybe it is a bug? Oliver Friedrich Consultant - Software Solutions -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: Mittwoch, 27. Juni 2007 12:59 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Conditions for setup in GUI and without GUI? You've set suppress=yes, which means the event doesn't occur. Rob Mailinglist wrote: Hi, Thank you for your hints, but this just doesn't work correctly. I do not need to create custom errors, if Condition statements do the same. So the helpful thoughts are in the lower part of your mail. That however does not work. If I set the UI_RAN property, the condition only fails if the NOT_WANTED_CONDITION fails. If the UI_RAN property is not set, it will fail anyhow, regardless of the NOT_WANTED_CONDITION. I tried the following: InstallExecuteSequence LaunchConditions Suppress='yes'NOT GUI/LaunchConditions /InstallExecuteSequence But that did'nt work either, since the condition NOT GUI seems to be simply ignored. Oliver Friedrich -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: Dienstag, 26. Juni 2007 17:17 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] [wix-users] Conditions for setup in GUI and without GUI? Yuo could create custom errors like this: Error Id=2000This is my error message/Error and create a custom action to trigger it like this: CustomAction Id=MyError Error=2000 / You can call this in the InstallExecuteSequence like this: Custom Action=MyErrorNOT WANTED_CONDITION /Custom The additional problem is how do you stop them triggering if the UI ran? You can create another CA like this: CustomAction Id=setUI_RAN Property=UI_RAN Value=1 / and schedule it at some point in the InstallUISequence (as long as it's before ExecuteAction). There's no need to declare the UI_RAN property; it will be created when the CA is run. The condition on your CA would then be something like: Custom Action=MyErrorNOT WANTED_CONDITION AND NOT UI_RAN/Custom Rob - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions for setup in GUI and without GUI?
Hi Rob, yes I was using throughout my code the GUI property, but referenced in my mail your UI_RAN property. Oliver Friedrich -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: Mittwoch, 27. Juni 2007 14:20 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Conditions for setup in GUI and without GUI? Just a sanity check. In your last message you said you were setting a UI_RAN property, but in your examples you're checking against a GUI property. You are setting and using the same property, right? Rob Mailinglist wrote: Hi Rob, You've set suppress=yes, which means the event doesn't occur. Last compile I tried the following: InstallExecuteSequence LaunchConditions Suppress='no'NOT (GUI=1)/LaunchConditions /InstallExecuteSequence And it did not work either, it fails with the specified message of the condition. Maybe it is a bug? Oliver Friedrich Consultant - Software Solutions -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: Mittwoch, 27. Juni 2007 12:59 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Conditions for setup in GUI and without GUI? You've set suppress=yes, which means the event doesn't occur. Rob Mailinglist wrote: Hi, Thank you for your hints, but this just doesn't work correctly. I do not need to create custom errors, if Condition statements do the same. So the helpful thoughts are in the lower part of your mail. That however does not work. If I set the UI_RAN property, the condition only fails if the NOT_WANTED_CONDITION fails. If the UI_RAN property is not set, it will fail anyhow, regardless of the NOT_WANTED_CONDITION. I tried the following: InstallExecuteSequence LaunchConditions Suppress='yes'NOT GUI/LaunchConditions /InstallExecuteSequence But that did'nt work either, since the condition NOT GUI seems to be simply ignored. Oliver Friedrich -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: Dienstag, 26. Juni 2007 17:17 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] [wix-users] Conditions for setup in GUI and without GUI? Yuo could create custom errors like this: Error Id=2000This is my error message/Error and create a custom action to trigger it like this: CustomAction Id=MyError Error=2000 / You can call this in the InstallExecuteSequence like this: Custom Action=MyErrorNOT WANTED_CONDITION /Custom The additional problem is how do you stop them triggering if the UI ran? You can create another CA like this: CustomAction Id=setUI_RAN Property=UI_RAN Value=1 / and schedule it at some point in the InstallUISequence (as long as it's before ExecuteAction). There's no need to declare the UI_RAN property; it will be created when the CA is run. The condition on your CA would then be something like: Custom Action=MyErrorNOT WANTED_CONDITION AND NOT UI_RAN/Custom Rob - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net
[WiX-users] [wix-users] Conditions for setup in GUI and without GUI?
Hi WiX-Users, in our Setup we use a personalized GUI, that checks in its first dialog several conditions and shows messages, if one condition fails. Most of this conditions handle previously needed software, like MMC 3.0 and Powershell 1.0. This just works fine for us, but if the install is done with /quiet parameter, those checks won't ever be run, since the dialog is not initialized anyway. So I tried of checking those conditions in the product itself, which works, but even while install with gui the messages pop up from the msi and not in our gui. How can I trigger the conditions to only be checked if the installation is done in quiet mode? Snippet of the project itself: !-- Launch conditions -- Condition Message='You have to be a local administrator to install $(var.AppName).' Privileged /Condition Condition Message=Windows XP or Windows Server 2003 or later is required. ![CDATA[VersionNT = 501]] /Condition Condition Message='This setup requires the .NET Framework 2.0 or higher.' ![CDATA[MsiNetAssemblySupport = 2.0.50727]] /Condition Condition Message=Microsoft SQL Server 2005 or SQL Server Express have to be present for this version to be installed. ![CDATA[ NOT(VERSIONFULLSQL) AND NOT(VERSIONEXPRESSSQL) ]] /Condition Condition Message='This setup requires the Microsoft Management Console 3.0 or higher.' ![CDATA[NOT(MMC3) AND NOT(VersionNT = 600)]] /Condition Condition Message='This setup requires the Microsoft Powershell v1.0 or higher.' ![CDATA[NOT (POWERSHELL)]] /Condition Snippet of the GUI with its conditions: Control Id=Next Type=PushButton X=236 Y=243 Width=56 Height=17 Default=yes Text=!(loc.WixUINext) Publish Event=NewDialog Value=[WixUI_WelcomeDlg_Next]1/Publish Condition Action=disable ![CDATA[ ((VersionNT 502) OR (VersionNT = 502 AND NOT(ServicePackLevel = 1))) ]] /Condition Condition Action=disable ![CDATA[ NOT(VERSIONFULLSQL) AND NOT(VERSIONEXPRESSSQL) ]] /Condition Condition Action=disable ![CDATA[NOT(MMC3) AND NOT(VersionNT = 600) ]] /Condition Condition Action=disable ![CDATA[NOT POWERSHELL]] /Condition Condition Action=enable ![CDATA[ ALLOWSERVER AND (VERSIONFULLSQL OR VERSIONEXPRESSSQL) AND (MMC3 OR (VersionNT = 600)) AND (POWERSHELL) AND NOT((VersionNT 502) OR (VersionNT = 502 AND NOT(ServicePackLevel = 1))) ]] /Condition Publish Property=IDIR Value=[NEWINSTALLDIR]Aldi-Ews\MSSERVER/Publish Publish Property=WixUI_InstallMode Value=InstallComplete/Publish /Control Any hints welcome. Oliver Friedrich Consultant - Software Solutions - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] [wix-users] Conditions for setup in GUI and without GUI?
Hmm, haven't seen that before. I've been using 2000+ for all my error codes. Should probably get round to fixing that some day, then. Rob Stefan Pavlik wrote: I know that the code below is just an example but to be precise: MSDN: Error Table The range from 25000 to 3 is reserved for errors from custom actions. Authors of custom actions may use this range for their custom actions. Regards Stefan Rob Hamflett wrote: Yuo could create custom errors like this: Error Id=2000This is my error message/Error and create a custom action to trigger it like this: CustomAction Id=MyError Error=2000 / You can call this in the InstallExecuteSequence like this: Custom Action=MyErrorNOT WANTED_CONDITION /Custom The additional problem is how do you stop them triggering if the UI ran? You can create another CA like this: CustomAction Id=setUI_RAN Property=UI_RAN Value=1 / and schedule it at some point in the InstallUISequence (as long as it's before ExecuteAction). There's no need to declare the UI_RAN property; it will be created when the CA is run. The condition on your CA would then be something like: Custom Action=MyErrorNOT WANTED_CONDITION AND NOT UI_RAN/Custom Rob Mailinglist wrote: Hi WiX-Users, in our Setup we use a personalized GUI, that checks in its first dialog several conditions and shows messages, if one condition fails. Most of this conditions handle previously needed software, like “MMC 3.0” and “Powershell 1.0”. This just works fine for us, but if the install is done with “/quiet” parameter, those checks won’t ever be run, since the dialog is not initialized anyway. So I tried of checking those conditions in the product itself, which works, but even while install with gui the messages pop up from the msi and not in our gui. How can I trigger the conditions to only be checked if the installation is done in quiet mode? Snippet of the project itself: !-- Launch conditions -- Condition Message='You have to be a local administrator to install $(var.AppName).' Privileged /Condition Condition Message=Windows XP or Windows Server 2003 or later is required. ![CDATA[VersionNT = 501]] /Condition Condition Message='This setup requires the .NET Framework 2.0 or higher.' ![CDATA[MsiNetAssemblySupport = 2.0.50727]] /Condition Condition Message=Microsoft SQL Server 2005 or SQL Server Express have to be present for this version to be installed. ![CDATA[ NOT(VERSIONFULLSQL) AND NOT(VERSIONEXPRESSSQL) ]] /Condition Condition Message='This setup requires the Microsoft Management Console 3.0 or higher.' ![CDATA[NOT(MMC3) AND NOT(VersionNT = 600)]] /Condition Condition Message='This setup requires the Microsoft Powershell v1.0 or higher.' ![CDATA[NOT (POWERSHELL)]] /Condition Snippet of the GUI with its conditions: Control Id=Next Type=PushButton X=236 Y=243 Width=56 Height=17 Default=yes Text=!(loc.WixUINext) Publish Event=NewDialog Value=[WixUI_WelcomeDlg_Next]1/Publish Condition Action=disable ![CDATA[ ((VersionNT 502) OR (VersionNT = 502 AND NOT(ServicePackLevel = 1))) ]] /Condition Condition Action=disable ![CDATA[ NOT(VERSIONFULLSQL) AND NOT(VERSIONEXPRESSSQL) ]] /Condition Condition Action=disable ![CDATA[NOT(MMC3) AND NOT(VersionNT = 600) ]] /Condition Condition Action=disable ![CDATA[NOT POWERSHELL]] /Condition Condition Action=enable ![CDATA[ ALLOWSERVER AND (VERSIONFULLSQL OR VERSIONEXPRESSSQL) AND (MMC3 OR (VersionNT = 600)) AND (POWERSHELL) AND NOT((VersionNT 502) OR (VersionNT = 502 AND NOT(ServicePackLevel = 1))) ]] /Condition Publish Property=IDIR Value=[NEWINSTALLDIR]Aldi-Ews\MSSERVER/Publish Publish Property=WixUI_InstallMode Value=InstallComplete/Publish /Control Any hints welcome. */Oliver Friedrich/* /Consultant - Software Solutions/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
Re: [WiX-users] [wix-users] Conditions for setup in GUI and without GUI?
Another info from MSDN (Windows Installer Error Messages): Windows Installer errors have an error code of 1000 or greater. The error codes numbered 1000 to 1999 are ship errors and must be authored into the Error table. The error codes numbered greater than 2000 are internal errors and do not have authored strings, but these can occur if the installation package has been incorrectly authored. For a list of reserved error codes, see Error table. Stefan Rob Hamflett wrote: Hmm, haven't seen that before. I've been using 2000+ for all my error codes. Should probably get round to fixing that some day, then. Rob Stefan Pavlik wrote: I know that the code below is just an example but to be precise: MSDN: Error Table The range from 25000 to 3 is reserved for errors from custom actions. Authors of custom actions may use this range for their custom actions. Regards Stefan Rob Hamflett wrote: Yuo could create custom errors like this: Error Id=2000This is my error message/Error and create a custom action to trigger it like this: CustomAction Id=MyError Error=2000 / You can call this in the InstallExecuteSequence like this: Custom Action=MyErrorNOT WANTED_CONDITION /Custom The additional problem is how do you stop them triggering if the UI ran? You can create another CA like this: CustomAction Id=setUI_RAN Property=UI_RAN Value=1 / and schedule it at some point in the InstallUISequence (as long as it's before ExecuteAction). There's no need to declare the UI_RAN property; it will be created when the CA is run. The condition on your CA would then be something like: Custom Action=MyErrorNOT WANTED_CONDITION AND NOT UI_RAN/Custom Rob Mailinglist wrote: Hi WiX-Users, in our Setup we use a personalized GUI, that checks in its first dialog several conditions and shows messages, if one condition fails. Most of this conditions handle previously needed software, like “MMC 3.0” and “Powershell 1.0”. This just works fine for us, but if the install is done with “/quiet” parameter, those checks won’t ever be run, since the dialog is not initialized anyway. So I tried of checking those conditions in the product itself, which works, but even while install with gui the messages pop up from the msi and not in our gui. How can I trigger the conditions to only be checked if the installation is done in quiet mode? Snippet of the project itself: !-- Launch conditions -- Condition Message='You have to be a local administrator to install $(var.AppName).' Privileged /Condition Condition Message=Windows XP or Windows Server 2003 or later is required. ![CDATA[VersionNT = 501]] /Condition Condition Message='This setup requires the .NET Framework 2.0 or higher.' ![CDATA[MsiNetAssemblySupport = 2.0.50727]] /Condition Condition Message=Microsoft SQL Server 2005 or SQL Server Express have to be present for this version to be installed. ![CDATA[ NOT(VERSIONFULLSQL) AND NOT(VERSIONEXPRESSSQL) ]] /Condition Condition Message='This setup requires the Microsoft Management Console 3.0 or higher.' ![CDATA[NOT(MMC3) AND NOT(VersionNT = 600)]] /Condition Condition Message='This setup requires the Microsoft Powershell v1.0 or higher.' ![CDATA[NOT (POWERSHELL)]] /Condition Snippet of the GUI with its conditions: Control Id=Next Type=PushButton X=236 Y=243 Width=56 Height=17 Default=yes Text=!(loc.WixUINext) Publish Event=NewDialog Value=[WixUI_WelcomeDlg_Next]1/Publish Condition Action=disable ![CDATA[ ((VersionNT 502) OR (VersionNT = 502 AND NOT(ServicePackLevel = 1))) ]] /Condition Condition Action=disable ![CDATA[ NOT(VERSIONFULLSQL) AND NOT(VERSIONEXPRESSSQL) ]] /Condition Condition Action=disable ![CDATA[NOT(MMC3) AND NOT(VersionNT = 600) ]] /Condition Condition Action=disable ![CDATA[NOT POWERSHELL]] /Condition Condition Action=enable ![CDATA[ ALLOWSERVER AND (VERSIONFULLSQL OR VERSIONEXPRESSSQL) AND (MMC3 OR (VersionNT = 600)) AND (POWERSHELL) AND NOT((VersionNT 502) OR (VersionNT = 502 AND NOT(ServicePackLevel = 1))) ]] /Condition Publish Property=IDIR Value=[NEWINSTALLDIR]Aldi-Ews\MSSERVER/Publish Publish Property=WixUI_InstallMode Value=InstallComplete/Publish /Control Any hints
[WiX-users] Conditions on Feature
I have features that I need changed based on user input. However they are based on information gained through my External UI sequence. Is there a way in code to call something that would produce the same results as Publish Event=AddLocalValue=FeatureId/ -- View this message in context: http://www.nabble.com/Conditions-on-Feature-tf3352983.html#a9324409 Sent from the wix-users mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions on Feature
MsiSetFeatureState? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Magus Sent: Monday, March 05, 2007 5:32 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditions on Feature I have features that I need changed based on user input. However they are based on information gained through my External UI sequence. Is there a way in code to call something that would produce the same results as Publish Event=AddLocalValue=FeatureId/ -- View this message in context: http://www.nabble.com/Conditions-on-Feature-tf3352983.html#a9324409 Sent from the wix-users mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditions for Custom Actions
Is there a way to conditionally run a custom action based on a property value? Property Id=PROP1 value=None / Custom action=""> So I want to run the custom action only if PROP1s value remains unchanged. Thanks Saranath - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions for Custom Actions
Yes. You don't need the square brackets around the Property. I suggest reading the MSI SDK topic about Condition Syntax. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Saranath Aravamudhan Sent: Saturday, September 23, 2006 00:50 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditions for Custom Actions Is there a way to conditionally run a custom action based on a property value? Property Id=PROP1 value=None / Custom action=""> So I want to run the custom action only if PROP1s value remains unchanged. Thanks Saranath - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditions and version of OS
Salut, trying to create my first setup using WIX. My software does not support Windows 95. In the http://www.tramontana.co.hu/wix/lesson1.php#1.4 wix tutorial I found the following lines: Condition Message='Operating system not supported!'Version9X = 400/Condition Condition Message='Operating system not supported!'Version9X = 400 AND WindowsBuild = /Condition Unfortunately I get the message Operating system not supported! when trying to run the setup, although I'm running Windows XP. What's wrong? By the way, can I replace the equality sign in the condition by a less than? Thanks in advance, Stefan -- View this message in context: http://www.nabble.com/Conditions-and-version-of-OS-tf2292721.html#a6368388 Sent from the wix-users mailing list archive at Nabble.com. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions and version of OS
In Wix, and with MSI installers in general I believe, the condition has to be *true* to install. So in these cases, you will *only* be able to install on Windows 95. I believe you want to change your '=' to 'NOT'. -Matt -Original Message- From: vbtricks [mailto:[EMAIL PROTECTED] Sent: Monday, September 18, 2006 10:31 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditions and version of OS Salut, trying to create my first setup using WIX. My software does not support Windows 95. In the http://www.tramontana.co.hu/wix/lesson1.php#1.4 wix tutorial I found the following lines: Condition Message='Operating system not supported!'Version9X = 400/Condition Condition Message='Operating system not supported!'Version9X = 400 AND WindowsBuild = /Condition Unfortunately I get the message Operating system not supported! when trying to run the setup, although I'm running Windows XP. What's wrong? By the way, can I replace the equality sign in the condition by a less than? Thanks in advance, Stefan -- View this message in context: http://www.nabble.com/Conditions-and-version-of-OS-tf2292721.html#a63683 88 Sent from the wix-users mailing list archive at Nabble.com. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditions and version of OS
Salut, thanks. I changed it to Condition Message='Operating system not supported!'Version9X = 400/Condition and it gives me no error anymore. Next time I get the chance to test it on Windows 95 I'll see if it works completely correct ;) Stefan Matthew Janulewicz-2 wrote: In Wix, and with MSI installers in general I believe, the condition has to be *true* to install. So in these cases, you will *only* be able to install on Windows 95. I believe you want to change your '=' to 'NOT'. -Matt -Original Message- From: vbtricks [mailto:[EMAIL PROTECTED] Sent: Monday, September 18, 2006 10:31 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditions and version of OS Salut, trying to create my first setup using WIX. My software does not support Windows 95. In the http://www.tramontana.co.hu/wix/lesson1.php#1.4 wix tutorial I found the following lines: Condition Message='Operating system not supported!'Version9X = 400/Condition Condition Message='Operating system not supported!'Version9X = 400 AND WindowsBuild = /Condition Unfortunately I get the message Operating system not supported! when trying to run the setup, although I'm running Windows XP. What's wrong? By the way, can I replace the equality sign in the condition by a less than? Thanks in advance, Stefan -- View this message in context: http://www.nabble.com/Conditions-and-version-of-OS-tf2292721.html#a63683 88 Sent from the wix-users mailing list archive at Nabble.com. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://www.nabble.com/Conditions-and-version-of-OS-tf2292721.html#a6368911 Sent from the wix-users mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] conditions
I see. How about just putting the component into Feature1 so that it will run when Feature1 is installed locally? Derek From: Scott Sam [mailto:[EMAIL PROTECTED] Sent: Friday, July 28, 2006 5:12 AM To: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] conditions I need to write out to a config file what features are being installed, so that the program that update/creates the database knows what database to create/update if any at all. From: Derek Cicerone [mailto:[EMAIL PROTECTED] Sent: Thursday, July 27, 2006 6:12 PM To: Scott Sam; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] conditions What are you trying to do overall? Using feature conditions in a components condition is a little awkward usually features directly determine if a component will be installed. Derek From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam Sent: Wednesday, July 26, 2006 12:25 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] conditions I have a component that looks like: Component Id=DbInstallationDirectoryService Guid=A4B5E633-D715-4e8e-8C4A-E58D1BAFFBAE XmlFile Action="" ElementPath=//DBInstallation/FeaturesInstalled File=[DBCREATION]dbinstallation.xml Id=dbInstallationConfig20 Name=Feature Sequence=19 Value=Feat1 / Condition![CDATA[(Feature1 = 3) AND (!Feature1 = 3)]]/Condition /Component From my understanding, it should right out FeatureFeat1/Feature if the Feature1 feature is being installed, and it is not an upgrade. That is not what is happening. What am I doing wrong? What is the best way to do this? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] conditions
I have a component that looks like: Component Id=DbInstallationDirectoryService Guid=A4B5E633-D715-4e8e-8C4A-E58D1BAFFBAE XmlFile Action="" ElementPath=//DBInstallation/FeaturesInstalled File=[DBCREATION]dbinstallation.xml Id=dbInstallationConfig20 Name=Feature Sequence=19 Value=Feat1 / Condition![CDATA[(Feature1 = 3) AND (!Feature1 = 3)]]/Condition /Component From my understanding, it should right out FeatureFeat1/Feature if the Feature1 feature is being installed, and it is not an upgrade. That is not what is happening. What am I doing wrong? What is the best way to do this? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] conditions
What are you trying to do overall? Using feature conditions in a components condition is a little awkward usually features directly determine if a component will be installed. Derek From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam Sent: Wednesday, July 26, 2006 12:25 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] conditions I have a component that looks like: Component Id=DbInstallationDirectoryService Guid=A4B5E633-D715-4e8e-8C4A-E58D1BAFFBAE XmlFile Action="" ElementPath=//DBInstallation/FeaturesInstalled File=[DBCREATION]dbinstallation.xml Id=dbInstallationConfig20 Name=Feature Sequence=19 Value=Feat1 / Condition![CDATA[(Feature1 = 3) AND (!Feature1 = 3)]]/Condition /Component From my understanding, it should right out FeatureFeat1/Feature if the Feature1 feature is being installed, and it is not an upgrade. That is not what is happening. What am I doing wrong? What is the best way to do this? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] conditions
I need to write out to a config file what features are being installed, so that the program that update/creates the database knows what database to create/update if any at all. From: Derek Cicerone [mailto:[EMAIL PROTECTED] Sent: Thursday, July 27, 2006 6:12 PM To: Scott Sam; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] conditions What are you trying to do overall? Using feature conditions in a components condition is a little awkward usually features directly determine if a component will be installed. Derek From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam Sent: Wednesday, July 26, 2006 12:25 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] conditions I have a component that looks like: Component Id=DbInstallationDirectoryService Guid=A4B5E633-D715-4e8e-8C4A-E58D1BAFFBAE XmlFile Action="" ElementPath=//DBInstallation/FeaturesInstalled File=[DBCREATION]dbinstallation.xml Id=dbInstallationConfig20 Name=Feature Sequence=19 Value=Feat1 / Condition![CDATA[(Feature1 = 3) AND (!Feature1 = 3)]]/Condition /Component From my understanding, it should right out FeatureFeat1/Feature if the Feature1 feature is being installed, and it is not an upgrade. That is not what is happening. What am I doing wrong? What is the best way to do this? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
