Re: [WiX-users] Command Line Parameters to Deferred CustomAction on Vista
They are still two separate items. SecureCustomProperties is need if you want to pass properties from the UI to the execute sequence, whether they get passed to custom actions or not. If you pass them to a immediate custom actions there's no need to use CustomActionData. So if you wanted to collect a property value in the UI sequence AND pass it to a deferred custom action then you'd need to use SCP to get it into the execute sequence AND use CustomActionData to pass it to a deferred custom action. You might be thinking that CustomActionData is a single property, but it's not. Every deferred custom action can have its own CustomActionData associated with it. Yes, it's used to pass property values into deferred custom actions. You simply cannot directly get property values in deferred custom actions, that's what CustomActionData is for. There'a a paragraph or two at the end here http://msdn.microsoft.com/en-us/library/aa370543(VS.85).aspx Phil Wilson -Original Message- From: Matt Walker [mailto:matt.wal...@synergis.com] Sent: Tuesday, September 21, 2010 6:45 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Command Line Parameters to Deferred CustomAction on Vista Since both worked in my scenario, I still, really don't know the difference. When you say SCPs is used to pass property values to the execute sequence, does that include access during or for deferred custom actions? Or, is CAD used to pass information to the deferred actions? Would there be a good example to illustrate the need for the use of CustomActionData where simply adding a property to SecureCustomProperties would not provide access during the deferred sequence? Any further help greatly appreciated. -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Tuesday, September 21, 2010 5:17 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Command Line Parameters to Deferred CustomAction on Vista Briefly, CustomActionData is a parameter passing scheme to get property values passed to a deferred custom action. SecureCustomProperties is a list of properties that you want to pass from the UI sequence (where you probably collected their values) across the context boundary into the execute sequence. Phil Wilson -Original Message- From: Superfreak3 [mailto:matt.wal...@synergis.com] Sent: Tuesday, September 21, 2010 11:59 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Command Line Parameters to Deferred Custom Action on Vista So what exactly is the difference between SecureCustomProperties and CustomActionData? I still do not fully understand this. We have a public property that holds a string that we write to the registry in certain cases. Is is held in the Property table. Let's say it contains 8.1.2.3 and is called OURVERSION. I have a little widget that runs near the end of the install that tests the condition for the registry edit and edits accordingly. I used a Set Property custom action sequenced in the Immediate Sequence to set the above mentioned property to something like PASSDATAACTION. Then, in the Deferrec Sequence action, I reference CustomActionData that now holds the value I passed. All seems to work OK here. I then thought, lets add the original property, OURVERSION, to SecureCustomProperties and just reference that directly as a parameter in my Deferred action, guess what. This works too. So, I'm unclear as to the true purpose of each. I know this really is off WiX topic, but I've gotten great help here before so any now is greatly appreciated. The scenario described above may not be exactly what is going on, but just to give an example. Thanks in advance for any help!! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Command-Li ne-Parameters-to-Deferred-Custom-Action-on-Vista-tp2652448p733.html Sent from the wix-users mailing list archive at Nabble.com. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ 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
Re: [WiX-users] Command Line Parameters toDeferred CustomAction on Vista
I guess I'm still a little foggy on it so I'll keep digging. If CustomActionData is needed to get values to Deferred Custom Actions, how then is my property value, populated in the Property Table, getting to my deferred action? In addition to having the property pre-populated in the table, I also added it to SecureCustomProperties. However I'm not using the Set Directory CA mechanism to get the value to CustomActionData. I don't know if I mentioned this before, but my Deferred Custom Action fires an .exe stored in the Binary Table with the following command line parameters being passed [ProductCode] [OURVERSION], the later being the pre-populated property. I don't know why, but I can't seem to get a handle on this! :( Matt Walker Installation Development 200 Kelly Road | Quakertown, PA 18951 Phone: +1 215.529.9900, x192 | 800.836.5440 Fax: +1 215.536.9249 http://www.synergissoftware.com/ Adept Engineering Document Management Workflow This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from us may be monitored. Internet communications cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Therefore, we do not accept responsibility for any errors or omissions that are present in this message, or any attachment, that have arisen as a result of e-mail transmission. If verification is required, please request a hard-copy version. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company. -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Wednesday, September 22, 2010 12:52 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Command Line Parameters toDeferred CustomAction on Vista They are still two separate items. SecureCustomProperties is need if you want to pass properties from the UI to the execute sequence, whether they get passed to custom actions or not. If you pass them to a immediate custom actions there's no need to use CustomActionData. So if you wanted to collect a property value in the UI sequence AND pass it to a deferred custom action then you'd need to use SCP to get it into the execute sequence AND use CustomActionData to pass it to a deferred custom action. You might be thinking that CustomActionData is a single property, but it's not. Every deferred custom action can have its own CustomActionData associated with it. Yes, it's used to pass property values into deferred custom actions. You simply cannot directly get property values in deferred custom actions, that's what CustomActionData is for. There'a a paragraph or two at the end here http://msdn.microsoft.com/en-us/library/aa370543(VS.85).aspx Phil Wilson -Original Message- From: Matt Walker [mailto:matt.wal...@synergis.com] Sent: Tuesday, September 21, 2010 6:45 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Command Line Parameters to Deferred CustomAction on Vista Since both worked in my scenario, I still, really don't know the difference. When you say SCPs is used to pass property values to the execute sequence, does that include access during or for deferred custom actions? Or, is CAD used to pass information to the deferred actions? Would there be a good example to illustrate the need for the use of CustomActionData where simply adding a property to SecureCustomProperties would not provide access during the deferred sequence? Any further help greatly appreciated. -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Tuesday, September 21, 2010 5:17 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Command Line Parameters to Deferred CustomAction on Vista Briefly, CustomActionData is a parameter passing scheme to get property values passed to a deferred custom action. SecureCustomProperties is a list of properties that you want to pass from the UI sequence (where you probably collected their values) across the context boundary into the execute sequence. Phil Wilson -Original Message- From: Superfreak3 [mailto:matt.wal...@synergis.com] Sent: Tuesday, September 21, 2010 11:59 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Command Line Parameters to Deferred Custom Action on Vista So what exactly is the difference
Re: [WiX-users] Command Line Parameters toDeferred CustomAction on Vista
On 22-Sep-10 13:07, Matt Walker wrote: I don't know if I mentioned this before, but my Deferred Custom Action fires an .exe stored in the Binary Table with the following command line parameters being passed [ProductCode] [OURVERSION], the later being the pre-populated property. The reason it works is that your deferred action is being scheduled during the script generation phase of the execute sequence, when properties are still available. Your CA isn't trying to read properties -- it's an .exe whose command line was set when it was scheduled. SecureCustomProperties is necessary to get a property out of the UI sequence and into the script generation phase of the execute sequence. SecureCustomProperties won't get a property into the *script execution* phase of the execute sequence; that's what CustomActionData is for. -- sig://boB http://joyofsetup.com/ -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Command Line Parameters to Deferred Custom Action on Vista
So what exactly is the difference between SecureCustomProperties and CustomActionData? I still do not fully understand this. We have a public property that holds a string that we write to the registry in certain cases. Is is held in the Property table. Let's say it contains 8.1.2.3 and is called OURVERSION. I have a little widget that runs near the end of the install that tests the condition for the registry edit and edits accordingly. I used a Set Property custom action sequenced in the Immediate Sequence to set the above mentioned property to something like PASSDATAACTION. Then, in the Deferrec Sequence action, I reference CustomActionData that now holds the value I passed. All seems to work OK here. I then thought, lets add the original property, OURVERSION, to SecureCustomProperties and just reference that directly as a parameter in my Deferred action, guess what. This works too. So, I'm unclear as to the true purpose of each. I know this really is off WiX topic, but I've gotten great help here before so any now is greatly appreciated. The scenario described above may not be exactly what is going on, but just to give an example. Thanks in advance for any help!! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Command-Line-Parameters-to-Deferred-Custom-Action-on-Vista-tp2652448p733.html Sent from the wix-users mailing list archive at Nabble.com. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Command Line Parameters to Deferred Custom Action on Vista
Briefly, CustomActionData is a parameter passing scheme to get property values passed to a deferred custom action. SecureCustomProperties is a list of properties that you want to pass from the UI sequence (where you probably collected their values) across the context boundary into the execute sequence. Phil Wilson -Original Message- From: Superfreak3 [mailto:matt.wal...@synergis.com] Sent: Tuesday, September 21, 2010 11:59 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Command Line Parameters to Deferred Custom Action on Vista So what exactly is the difference between SecureCustomProperties and CustomActionData? I still do not fully understand this. We have a public property that holds a string that we write to the registry in certain cases. Is is held in the Property table. Let's say it contains 8.1.2.3 and is called OURVERSION. I have a little widget that runs near the end of the install that tests the condition for the registry edit and edits accordingly. I used a Set Property custom action sequenced in the Immediate Sequence to set the above mentioned property to something like PASSDATAACTION. Then, in the Deferrec Sequence action, I reference CustomActionData that now holds the value I passed. All seems to work OK here. I then thought, lets add the original property, OURVERSION, to SecureCustomProperties and just reference that directly as a parameter in my Deferred action, guess what. This works too. So, I'm unclear as to the true purpose of each. I know this really is off WiX topic, but I've gotten great help here before so any now is greatly appreciated. The scenario described above may not be exactly what is going on, but just to give an example. Thanks in advance for any help!! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Command-Line-Parameters-to-Deferred-Custom-Action-on-Vista-tp2652448p733.html Sent from the wix-users mailing list archive at Nabble.com. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77nav_id=80prev_id=77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Command Line Parameters to Deferred CustomAction on Vista
Since both worked in my scenario, I still, really don't know the difference. When you say SCPs is used to pass property values to the execute sequence, does that include access during or for deferred custom actions? Or, is CAD used to pass information to the deferred actions? Would there be a good example to illustrate the need for the use of CustomActionData where simply adding a property to SecureCustomProperties would not provide access during the deferred sequence? Any further help greatly appreciated. -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Tuesday, September 21, 2010 5:17 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Command Line Parameters to Deferred CustomAction on Vista Briefly, CustomActionData is a parameter passing scheme to get property values passed to a deferred custom action. SecureCustomProperties is a list of properties that you want to pass from the UI sequence (where you probably collected their values) across the context boundary into the execute sequence. Phil Wilson -Original Message- From: Superfreak3 [mailto:matt.wal...@synergis.com] Sent: Tuesday, September 21, 2010 11:59 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Command Line Parameters to Deferred Custom Action on Vista So what exactly is the difference between SecureCustomProperties and CustomActionData? I still do not fully understand this. We have a public property that holds a string that we write to the registry in certain cases. Is is held in the Property table. Let's say it contains 8.1.2.3 and is called OURVERSION. I have a little widget that runs near the end of the install that tests the condition for the registry edit and edits accordingly. I used a Set Property custom action sequenced in the Immediate Sequence to set the above mentioned property to something like PASSDATAACTION. Then, in the Deferrec Sequence action, I reference CustomActionData that now holds the value I passed. All seems to work OK here. I then thought, lets add the original property, OURVERSION, to SecureCustomProperties and just reference that directly as a parameter in my Deferred action, guess what. This works too. So, I'm unclear as to the true purpose of each. I know this really is off WiX topic, but I've gotten great help here before so any now is greatly appreciated. The scenario described above may not be exactly what is going on, but just to give an example. Thanks in advance for any help!! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Command-Li ne-Parameters-to-Deferred-Custom-Action-on-Vista-tp2652448p733.html Sent from the wix-users mailing list archive at Nabble.com. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77nav_id=80prev_i d=77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Start uncovering the many advantages of virtual appliances and start using them
Re: [WiX-users] Command Line Parameters to Deferred Custom Action on Vista
For deferred custom actions you pass parameters through CustomActionData. See http://blogs.technet.com/alexshev/archive/2008/03/25/property-does-not-exist-or-empty-when-accessed-from-deferred-custom-action.aspx for details. Alex -Original Message- From: Rajesh P [mailto:rajeshp.bl...@gmail.com] Sent: Friday, April 17, 2009 12:15 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Command Line Parameters to Deferred Custom Action on Vista Hi, I am developing a WiX installer for Vista. I have a requirement to send some command line parameters to a Deferred Cusom action. My inital attempts to send the parameters using public property as follows have failed: I tried : msiexec /i myinstaller.msi CMDLINEPROPERTY=arg1 arg2 arg3 But till now i have not been able to get these arguments reach my custom action where i am calling MSIGetProperty() go retrievet the property value. I even tried reading the value from CustomActionData property , but no success yet. If anyone has successfully achieved this on a Vista platform , please help me !! Thanking you in Advance, Rajesh -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Command Line Parameters to Deferred Custom Action on Vista
Rajesh P wrote: I am developing a WiX installer for Vista. I have a requirement to send some command line parameters to a Deferred Cusom action. Then you must use CustomActionData; deferred custom actions can't otherwise get property values. -- sig://boB http://joyofsetup.com/ -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Command Line Parameters to Deferred Custom Action on Vista
Hi, I am developing a WiX installer for Vista. I have a requirement to send some command line parameters to a Deferred Cusom action. My inital attempts to send the parameters using public property as follows have failed: I tried : msiexec /i myinstaller.msi CMDLINEPROPERTY=arg1 arg2 arg3 But till now i have not been able to get these arguments reach my custom action where i am calling MSIGetProperty() go retrievet the property value. I even tried reading the value from CustomActionData property , but no success yet. If anyone has successfully achieved this on a Vista platform , please help me !! Thanking you in Advance, Rajesh -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Command Line Parameters to Deferred Custom Action on Vista
If you are referencing that property in a custom action in the InstallExecute sequence you need to add it to the SecureCustomProperties list - this gets properties and their values across the UI=Execute sequence boundary. Phil Wilson -Original Message- From: Rajesh P [mailto:rajeshp.bl...@gmail.com] Sent: Friday, April 17, 2009 12:15 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Command Line Parameters to Deferred Custom Action on Vista Hi, I am developing a WiX installer for Vista. I have a requirement to send some command line parameters to a Deferred Cusom action. My inital attempts to send the parameters using public property as follows have failed: I tried : msiexec /i myinstaller.msi CMDLINEPROPERTY=arg1 arg2 arg3 But till now i have not been able to get these arguments reach my custom action where i am calling MSIGetProperty() go retrievet the property value. I even tried reading the value from CustomActionData property , but no success yet. If anyone has successfully achieved this on a Vista platform , please help me !! Thanking you in Advance, Rajesh -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Command line parameters
I have 2 public properties in my MSI file. Each property is set a default value as well has a registrysearch to find a value.. e.g. Property Id=MDBFULLPATH Value=C:\Program Files\eProject\database\eProject - empty.mdb RegistrySearch Id=MDBPathRegistry Type=raw Root=HKLM Key=Software\eProject Name=DataSource / /Property What I want to be able to do is pass in a value for this property from the command line but that only works when RegistrySearch is commented out. If the RegistrySeach returns a value then that should be used, else the command line value should be used, else the defautl Value should be used as a last resort. Is this possible? Russ -- View this message in context: http://www.nabble.com/Command-line-parameters-tf4666532.html#a13330344 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Command line parameters
You could use 3 different properties. One for the command line, one for the registrysearch, and one for the default. Then have two set property custom actions conditioned on whether or not the command line property is set or if the registrysearch property is set. If they are, then you would set the default property to that value using the custom action. You can order them in the order you need to in order to get the precedence you want. Then just use the default property everywhere else. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of RussGreen Sent: Sunday, October 21, 2007 8:56 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Command line parameters I have 2 public properties in my MSI file. Each property is set a default value as well has a registrysearch to find a value.. e.g. Property Id=MDBFULLPATH Value=C:\Program Files\eProject\database\eProject - empty.mdb RegistrySearch Id=MDBPathRegistry Type=raw Root=HKLM Key=Software\eProject Name=DataSource / /Property What I want to be able to do is pass in a value for this property from the command line but that only works when RegistrySearch is commented out. If the RegistrySeach returns a value then that should be used, else the command line value should be used, else the defautl Value should be used as a last resort. Is this possible? Russ -- View this message in context: http://www.nabble.com/Command-line-parameters-tf4666532.html#a13330344 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Command line parameters
In article [EMAIL PROTECTED], RussGreen [EMAIL PROTECTED] writes: What I want to be able to do is pass in a value for this property from the command line but that only works when RegistrySearch is commented out. As Peter Marcu suggested, use a different property for the value retrieved from the registry so that you can differentiate when the value was set from the command-line and when the value needs to come from the registry. -- The Direct3D Graphics Pipeline -- DirectX 9 draft available for download http://www.xmission.com/~legalize/book/download/index.html Legalize Adulthood! http://blogs.xmission.com/legalize/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Command line parameters
Ah so simple -- View this message in context: http://www.nabble.com/Command-line-parameters-tf4666532.html#a13332073 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
