Re: [WiX-users] Some in burn wixstba similar to msiexec /xProductCode

2012-10-15 Thread Michael Ogilvie
Does v3.6 have the bundle self-update feature or only v3.7?


Thank you,
Michael Ogilvie
Application Support Specialist | PixeLINK

1900 City Park Drive, Suite 410.
Ottawa, Ontario K1J 1A3

tel: 613.247.1211 Ext. 242 |  cell: 613.302.9844 | fax: 613.247.2001 | skype: 
pixelink.mogilvie
www.pixelink.com


-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: Monday, October 15, 2012 1:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Some in burn wixstba similar to msiexec /xProductCode

Having the update URL come from outside the Bundle would be a very large 
security gap. Essentially, any Bundle could be used to launch any other random 
Bundle. That's not right.  There is certainly work that could be done in the 
wixstdba to support bundle self-update but I don't think passing the update 
URL via the command-line is the right way to do that.
smile/

On Sun, Oct 14, 2012 at 5:56 PM, Wesley Manning wmann...@dynagen.ca wrote:

 Sorry, for (1) I meant I don't want to do it from a custom BA. I want 
 to do it by calling the bundle from the application software that my 
 bundle installs.  I know for wixstba you provide /uninstall and /repair 
 commands.
  I use wixstba for my bundle so it would be nice if there was an /upgrade
 command line option in wixstba where I pass the URL of the update and 
 the bundle downloads and installs it.  Is this something that you guys 
 can do for version 3.7?

 Thanks for the info on UninstallKey in the registry.  I actually 
 forgot about that.  I see it has a  BundleCachePath value so I can use 
 that to call  my bundle.  All I need is for the wixstba to have a 
 command line argument to do an upgrade.  Questions 2 and 3 are moot now.

 Wes

 -Original Message-
 From: Rob Mensching [mailto:r...@robmensching.com]
 Sent: October 14, 2012 12:37 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Some in burn wixstba similar to msiexec /x 
 ProductCode

 1. I don't quite understand the question. The bundle self-update 
 feature allows a BA to check the internet and tell the engine that 
 there is a newer version of itself and to download then launch that 
 instead. It is not clear to me what the command-line has to do with it.

 2. Bundles are registered in ARP (aka: Program and Features, aka: the 
 UninstallKey). That's how you can click on the Uninstall button in 
 ARP and Burn launches to remove the bundle. You can search for it that 
 way if you want.

 3. Again, the self-update happens inside a Burn bundle. It isn't 
 driven from a command-line argument. I may just be confused by not 
 understanding your first question.

 You always have the Bundle. It's cached. That's how ARP works.

 On Fri, Oct 12, 2012 at 10:44 AM, Wesley Manning wmann...@dynagen.ca
 wrote:

  Hi, have some questions about wixstba:
 
  (1) Wix 3.7 bundle self update feature:  Is it possible (or any 
  plans to make it possible) to run from the command line?  You would 
  need to run the bundle exe (thus have to know where its located).  
  There is already -uninstall, -repair, etc.
  (2) Since Windows installer is part of the operating system it is 
  possible to install/uninstall/repair by running msiexec /x 
  ProductCode.  You don't need to have the MSi file or know where it 
  is on the computer.  Is there something similar for bundles?  This 
  question is really about burn in general.
  (3) Similar to (2) above but for the wix 3.7 self update feature: 
  give an upgrade code and URL and have it download and upgrade the bundle.
  Is this possible?
 
  I was hoping to have our software update itself / show its own 
  install progress UI so the user doesn't have to use the bundle for 
  that (they may not have the bundle anymore).  The bundle would only 
  be used to install our software on a clean computer or if user goes 
  to ARP they can interact with the bundle.  I see in 
  Wix37\src\burn\Samples there is an example on how to get progress from burn.
 
  I could write code to download the burn exe myself but burn can 
  already download updates so...
 
  Wes
 
  -Original Message-
  From: James Johnston [mailto:johnst...@inn-soft.com]
  Sent: October-12-12 1:15 PM
  To: wix-users@lists.sourceforge.net
  Subject: [WiX-users] Broken links on WiX web site
 
  Hi,
 
  The page at:
  http://wix.sourceforge.net/manual-wix3/WixUI_dialog_library.htm
  contains some broken links.  Specifically, WixUI_Mondo and 
  WixUI_Minimal are broken (404 Not Found).
 
  Not sure who maintains the web site so I'm writing to this list...
 
  Best regards,
 
  James Johnston
 
 
 
  
  --
   Don't let slow site performance ruin your business. Deploy 
  New Relic APM Deploy New Relic app performance management and know 
  exactly what is happening inside your Ruby, Python, PHP, Java, and 
  .NET app Try New Relic at no cost

Re: [WiX-users] Some in burn wixstba similar to msiexec /xProductCode

2012-10-15 Thread Rob Mensching
New feature in v3.7:
http://robmensching.com/blog/posts/2012/8/21/Enter-WiX-v3.7-toolset

On Mon, Oct 15, 2012 at 10:29 AM, Michael Ogilvie 
michael.ogil...@pixelink.com wrote:

 Does v3.6 have the bundle self-update feature or only v3.7?


 Thank you,
 Michael Ogilvie
 Application Support Specialist | PixeLINK

 1900 City Park Drive, Suite 410.
 Ottawa, Ontario K1J 1A3

 tel: 613.247.1211 Ext. 242 |  cell: 613.302.9844 | fax: 613.247.2001 |
 skype: pixelink.mogilvie
 www.pixelink.com


 -Original Message-
 From: Rob Mensching [mailto:r...@robmensching.com]
 Sent: Monday, October 15, 2012 1:17 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Some in burn wixstba similar to msiexec
 /xProductCode

 Having the update URL come from outside the Bundle would be a very large
 security gap. Essentially, any Bundle could be used to launch any other
 random Bundle. That's not right.  There is certainly work that could be
 done in the wixstdba to support bundle self-update but I don't think
 passing the update URL via the command-line is the right way to do that.
 smile/

 On Sun, Oct 14, 2012 at 5:56 PM, Wesley Manning wmann...@dynagen.ca
 wrote:

  Sorry, for (1) I meant I don't want to do it from a custom BA. I want
  to do it by calling the bundle from the application software that my
  bundle installs.  I know for wixstba you provide /uninstall and /repair
 commands.
   I use wixstba for my bundle so it would be nice if there was an
 /upgrade
  command line option in wixstba where I pass the URL of the update and
  the bundle downloads and installs it.  Is this something that you guys
  can do for version 3.7?
 
  Thanks for the info on UninstallKey in the registry.  I actually
  forgot about that.  I see it has a  BundleCachePath value so I can use
  that to call  my bundle.  All I need is for the wixstba to have a
  command line argument to do an upgrade.  Questions 2 and 3 are moot now.
 
  Wes
 
  -Original Message-
  From: Rob Mensching [mailto:r...@robmensching.com]
  Sent: October 14, 2012 12:37 AM
  To: General discussion for Windows Installer XML toolset.
  Subject: Re: [WiX-users] Some in burn wixstba similar to msiexec /x
  ProductCode
 
  1. I don't quite understand the question. The bundle self-update
  feature allows a BA to check the internet and tell the engine that
  there is a newer version of itself and to download then launch that
  instead. It is not clear to me what the command-line has to do with it.
 
  2. Bundles are registered in ARP (aka: Program and Features, aka: the
  UninstallKey). That's how you can click on the Uninstall button in
  ARP and Burn launches to remove the bundle. You can search for it that
  way if you want.
 
  3. Again, the self-update happens inside a Burn bundle. It isn't
  driven from a command-line argument. I may just be confused by not
  understanding your first question.
 
  You always have the Bundle. It's cached. That's how ARP works.
 
  On Fri, Oct 12, 2012 at 10:44 AM, Wesley Manning wmann...@dynagen.ca
  wrote:
 
   Hi, have some questions about wixstba:
  
   (1) Wix 3.7 bundle self update feature:  Is it possible (or any
   plans to make it possible) to run from the command line?  You would
   need to run the bundle exe (thus have to know where its located).
   There is already -uninstall, -repair, etc.
   (2) Since Windows installer is part of the operating system it is
   possible to install/uninstall/repair by running msiexec /x
   ProductCode.  You don't need to have the MSi file or know where it
   is on the computer.  Is there something similar for bundles?  This
   question is really about burn in general.
   (3) Similar to (2) above but for the wix 3.7 self update feature:
   give an upgrade code and URL and have it download and upgrade the
 bundle.
   Is this possible?
  
   I was hoping to have our software update itself / show its own
   install progress UI so the user doesn't have to use the bundle for
   that (they may not have the bundle anymore).  The bundle would only
   be used to install our software on a clean computer or if user goes
   to ARP they can interact with the bundle.  I see in
   Wix37\src\burn\Samples there is an example on how to get progress from
 burn.
  
   I could write code to download the burn exe myself but burn can
   already download updates so...
  
   Wes
  
   -Original Message-
   From: James Johnston [mailto:johnst...@inn-soft.com]
   Sent: October-12-12 1:15 PM
   To: wix-users@lists.sourceforge.net
   Subject: [WiX-users] Broken links on WiX web site
  
   Hi,
  
   The page at:
   http://wix.sourceforge.net/manual-wix3/WixUI_dialog_library.htm
   contains some broken links.  Specifically, WixUI_Mondo and
   WixUI_Minimal are broken (404 Not Found).
  
   Not sure who maintains the web site so I'm writing to this list...
  
   Best regards,
  
   James Johnston

Re: [WiX-users] Some in burn wixstba similar to msiexec/xProductCode

2012-10-15 Thread Michael Ogilvie
Thanks,

I will try updating again and hopefully I don't have more issues


Thank you,
Michael Ogilvie
Application Support Specialist | PixeLINK

1900 City Park Drive, Suite 410.
Ottawa, Ontario K1J 1A3

tel: 613.247.1211 Ext. 242 |  cell: 613.302.9844 | fax: 613.247.2001 | skype: 
pixelink.mogilvie
www.pixelink.com


-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: Monday, October 15, 2012 1:39 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Some in burn wixstba similar to msiexec/xProductCode

New feature in v3.7:
http://robmensching.com/blog/posts/2012/8/21/Enter-WiX-v3.7-toolset

On Mon, Oct 15, 2012 at 10:29 AM, Michael Ogilvie  
michael.ogil...@pixelink.com wrote:

 Does v3.6 have the bundle self-update feature or only v3.7?


 Thank you,
 Michael Ogilvie
 Application Support Specialist | PixeLINK

 1900 City Park Drive, Suite 410.
 Ottawa, Ontario K1J 1A3

 tel: 613.247.1211 Ext. 242 |  cell: 613.302.9844 | fax: 613.247.2001 |
 skype: pixelink.mogilvie
 www.pixelink.com


 -Original Message-
 From: Rob Mensching [mailto:r...@robmensching.com]
 Sent: Monday, October 15, 2012 1:17 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Some in burn wixstba similar to msiexec 
 /xProductCode

 Having the update URL come from outside the Bundle would be a very 
 large security gap. Essentially, any Bundle could be used to launch 
 any other random Bundle. That's not right.  There is certainly work 
 that could be done in the wixstdba to support bundle self-update but 
 I don't think passing the update URL via the command-line is the right way to 
 do that.
 smile/

 On Sun, Oct 14, 2012 at 5:56 PM, Wesley Manning wmann...@dynagen.ca
 wrote:

  Sorry, for (1) I meant I don't want to do it from a custom BA. I 
  want to do it by calling the bundle from the application software 
  that my bundle installs.  I know for wixstba you provide /uninstall 
  and /repair
 commands.
   I use wixstba for my bundle so it would be nice if there was an
 /upgrade
  command line option in wixstba where I pass the URL of the update 
  and the bundle downloads and installs it.  Is this something that 
  you guys can do for version 3.7?
 
  Thanks for the info on UninstallKey in the registry.  I actually 
  forgot about that.  I see it has a  BundleCachePath value so I can 
  use that to call  my bundle.  All I need is for the wixstba to have 
  a command line argument to do an upgrade.  Questions 2 and 3 are moot now.
 
  Wes
 
  -Original Message-
  From: Rob Mensching [mailto:r...@robmensching.com]
  Sent: October 14, 2012 12:37 AM
  To: General discussion for Windows Installer XML toolset.
  Subject: Re: [WiX-users] Some in burn wixstba similar to msiexec /x 
  ProductCode
 
  1. I don't quite understand the question. The bundle self-update 
  feature allows a BA to check the internet and tell the engine that 
  there is a newer version of itself and to download then launch that 
  instead. It is not clear to me what the command-line has to do with it.
 
  2. Bundles are registered in ARP (aka: Program and Features, aka: 
  the UninstallKey). That's how you can click on the Uninstall 
  button in ARP and Burn launches to remove the bundle. You can search 
  for it that way if you want.
 
  3. Again, the self-update happens inside a Burn bundle. It isn't 
  driven from a command-line argument. I may just be confused by not 
  understanding your first question.
 
  You always have the Bundle. It's cached. That's how ARP works.
 
  On Fri, Oct 12, 2012 at 10:44 AM, Wesley Manning 
  wmann...@dynagen.ca
  wrote:
 
   Hi, have some questions about wixstba:
  
   (1) Wix 3.7 bundle self update feature:  Is it possible (or any 
   plans to make it possible) to run from the command line?  You 
   would need to run the bundle exe (thus have to know where its located).
   There is already -uninstall, -repair, etc.
   (2) Since Windows installer is part of the operating system it is 
   possible to install/uninstall/repair by running msiexec /x 
   ProductCode.  You don't need to have the MSi file or know where it 
   is on the computer.  Is there something similar for bundles?  This 
   question is really about burn in general.
   (3) Similar to (2) above but for the wix 3.7 self update feature:
   give an upgrade code and URL and have it download and upgrade the
 bundle.
   Is this possible?
  
   I was hoping to have our software update itself / show its own 
   install progress UI so the user doesn't have to use the bundle for 
   that (they may not have the bundle anymore).  The bundle would 
   only be used to install our software on a clean computer or if 
   user goes to ARP they can interact with the bundle.  I see in 
   Wix37\src\burn\Samples there is an example on how to get progress 
   from
 burn.
  
   I could write code to download the burn exe myself but burn can 
   already download updates so

Re: [WiX-users] Some in burn wixstba similar to msiexec/xProductCode

2012-10-15 Thread Hoover, Jacob
3.7 is in a development/potentially unstable state, so I wouldn't upgrade to 
3.7 for a production deployment as of yet.

-Original Message-
From: Michael Ogilvie [mailto:michael.ogil...@pixelink.com] 
Sent: Monday, October 15, 2012 12:45 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Some in burn wixstba similar to msiexec/xProductCode

Thanks,

I will try updating again and hopefully I don't have more issues


Thank you,
Michael Ogilvie
Application Support Specialist | PixeLINK

1900 City Park Drive, Suite 410.
Ottawa, Ontario K1J 1A3

tel: 613.247.1211 Ext. 242 |  cell: 613.302.9844 | fax: 613.247.2001 | skype: 
pixelink.mogilvie www.pixelink.com


-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Monday, October 15, 2012 1:39 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Some in burn wixstba similar to msiexec/xProductCode

New feature in v3.7:
http://robmensching.com/blog/posts/2012/8/21/Enter-WiX-v3.7-toolset

On Mon, Oct 15, 2012 at 10:29 AM, Michael Ogilvie  
michael.ogil...@pixelink.com wrote:

 Does v3.6 have the bundle self-update feature or only v3.7?


 Thank you,
 Michael Ogilvie
 Application Support Specialist | PixeLINK

 1900 City Park Drive, Suite 410.
 Ottawa, Ontario K1J 1A3

 tel: 613.247.1211 Ext. 242 |  cell: 613.302.9844 | fax: 613.247.2001 |
 skype: pixelink.mogilvie
 www.pixelink.com


 -Original Message-
 From: Rob Mensching [mailto:r...@robmensching.com]
 Sent: Monday, October 15, 2012 1:17 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Some in burn wixstba similar to msiexec 
 /xProductCode

 Having the update URL come from outside the Bundle would be a very 
 large security gap. Essentially, any Bundle could be used to launch 
 any other random Bundle. That's not right.  There is certainly work 
 that could be done in the wixstdba to support bundle self-update but 
 I don't think passing the update URL via the command-line is the right way to 
 do that.
 smile/

 On Sun, Oct 14, 2012 at 5:56 PM, Wesley Manning wmann...@dynagen.ca
 wrote:

  Sorry, for (1) I meant I don't want to do it from a custom BA. I 
  want to do it by calling the bundle from the application software 
  that my bundle installs.  I know for wixstba you provide /uninstall 
  and /repair
 commands.
   I use wixstba for my bundle so it would be nice if there was an
 /upgrade
  command line option in wixstba where I pass the URL of the update 
  and the bundle downloads and installs it.  Is this something that 
  you guys can do for version 3.7?
 
  Thanks for the info on UninstallKey in the registry.  I actually 
  forgot about that.  I see it has a  BundleCachePath value so I can 
  use that to call  my bundle.  All I need is for the wixstba to have 
  a command line argument to do an upgrade.  Questions 2 and 3 are moot now.
 
  Wes
 
  -Original Message-
  From: Rob Mensching [mailto:r...@robmensching.com]
  Sent: October 14, 2012 12:37 AM
  To: General discussion for Windows Installer XML toolset.
  Subject: Re: [WiX-users] Some in burn wixstba similar to msiexec /x 
  ProductCode
 
  1. I don't quite understand the question. The bundle self-update 
  feature allows a BA to check the internet and tell the engine that 
  there is a newer version of itself and to download then launch that 
  instead. It is not clear to me what the command-line has to do with it.
 
  2. Bundles are registered in ARP (aka: Program and Features, aka: 
  the UninstallKey). That's how you can click on the Uninstall 
  button in ARP and Burn launches to remove the bundle. You can search 
  for it that way if you want.
 
  3. Again, the self-update happens inside a Burn bundle. It isn't 
  driven from a command-line argument. I may just be confused by not 
  understanding your first question.
 
  You always have the Bundle. It's cached. That's how ARP works.
 
  On Fri, Oct 12, 2012 at 10:44 AM, Wesley Manning 
  wmann...@dynagen.ca
  wrote:
 
   Hi, have some questions about wixstba:
  
   (1) Wix 3.7 bundle self update feature:  Is it possible (or any 
   plans to make it possible) to run from the command line?  You 
   would need to run the bundle exe (thus have to know where its located).
   There is already -uninstall, -repair, etc.
   (2) Since Windows installer is part of the operating system it is 
   possible to install/uninstall/repair by running msiexec /x 
   ProductCode.  You don't need to have the MSi file or know where it 
   is on the computer.  Is there something similar for bundles?  This 
   question is really about burn in general.
   (3) Similar to (2) above but for the wix 3.7 self update feature:
   give an upgrade code and URL and have it download and upgrade the
 bundle.
   Is this possible?
  
   I was hoping to have our software update itself / show its own 
   install progress UI so the user doesn't have to use the bundle