If the bundle determines that a package should be installed, then it
downloads the package to a local folder and installs it. You can specify
whether you want the package cached locally, but the recommended practice
(as I have read elsewhere) is to leave the cache attribute unspecified and
let bur
Hi Phill,
When I use the DownloadUrl attribute, does the chainedproduct.msi get
actully downloaded to the user's machine or is it installed from the remote
location?
Thanks & Regards,
Prantik Sarmah
On Mon, Apr 21, 2014 at 6:23 PM, Prantik Sarmah <
prantik.sar...@grapecity.com> wrote:
> Than
I am in the process of doing a similar conversion, and am very happy with the
wix model of moving the UI to the bootstrapper application and having
smaller MSI packages for each application (or feature), chained. So I can
add my 2 cents, and others can provide more details.
When you use the Cha
Our company releases products where the MSIs are pretty large in size.In
order to reduce the customer's cost of installation,we are planning to move
towards a WebInstallation model and I am thinking of the following way.
1) Segregete Product1.msi into multiple sub msis
(Section1.msi,Section2.msi..
Thank you. It works now.
Thanks & Regards,
Prantik Sarmah
On Mon, Apr 21, 2014 at 4:31 PM, Phill Hogland wrote:
> Use something along these lines:
> Vital='yes'
> Compressed='no'
> DownloadUrl="http://10.64.2.42/t/Products/{2}";
>
Use something along these lines:
http://10.64.2.42/t/Products/{2}";
SourceFile='path_to_I1\I1.msi'
InstallCondition='evaluatetes_to_1 = 1'
>
SourcePath is the location of your package at build time.
DownloadURL is the location where you
Hi,
I am a new-bie to wix. I need to install two msies from web through a
chained installation. My wxs is as below.
http://schemas.microsoft.com/wix/2006/wi";>
http://10.64.2.42/t/Products/I1.msi"/>
http://10.64.2.42/t/Products/2.msi";
/>
7 matches
Mail list logo
