Re: [WiX-users] Wix 3.6 Burn MsiPackage Basic Quesiton

2012-06-15 Thread Rob Mensching
The way to implement this is to download a new Bundle. The WiX toolset's install basically does this via the "Check Updates" tile in the bottom left. We don't automatically get the latest in the WiX toolset's install but could have... On Fri, Jun 15, 2012 at 10:40 AM, yojam wrote: > We have a si

Re: [WiX-users] Wix 3.6 Burn MsiPackage Basic Quesiton

2012-06-15 Thread yojam
We have a similar requirement in order to download latest versions (hosted in DownloadURL) and we cannot redistribute the bundle installer (will be pre-installed on certain platforms). Would it be possible to change this hash/file validation by implementing a custom Boostrapper Application? Thanks

Re: [WiX-users] Wix 3.6 Burn MsiPackage Basic Quesiton

2011-05-02 Thread Rob Mensching
No. Burn doesn't currently work that way. Instead, the design is to update the bootstrapper and publish it pointing to new binaries. That way you can handle the case where previous versions of the bootstrapper are installed and get the new MSIs installed everywhere. On Thu, Apr 21, 2011 at 9:18 AM

[WiX-users] Wix 3.6 Burn MsiPackage Basic Quesiton

2011-04-21 Thread Maillet, Ed
Hey all, I'm using Burn in Wix 3.6.1615.0 and just trying to understand the basics. I have two MSIs (A & B) and I'm using the MsiPackage element as such: http://server:8077/BurnA.msi"; Cache="no" Compressed="no"> http://server:8077/BurnB.msi"; Cache="no" Compressed="no"> Since SourceFile a