Thanks Neil, I knew security would be an issue / can of worms, but at least I
can now stop looking for something that doesn't exist :)
Cheers again.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-create-and-reference-a-custom-pre-requisite
Support for username/password is not available today, you could add it to
the url using something like http://username:passw...@site.com/ (not sure
this work but might be worth trying).
I would point out that it won't be very secure as the contents of the
bundle could be extracted to reveal the pa
OK thanks, I think I'm getting there
So, I have my MsiPackage for my download...
https://mycompany.com/downloads/blahblah/sharedcomponents.msi";
DisplayName="Shared Components"
Compressed="no"
Vital="yes">
One piece of missing info I cannot find in the docume
MsiPackage/@Compressed = No
-Original Message-
From: Spud [mailto:andysmi...@gmail.com]
Sent: Tuesday, April 09, 2013 10:09 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to create and reference a custom pre-requisite
package
Hi Raj, thanks for your response.
I
Hi Raj, thanks for your response.
I can put all the third party components in their own MSI (in fact I have
now done just that) but since the MSI is currently within the
Bootstrapper.exe its self it will always get downloaded with each update.
*How* do I set this "thirdpartycomponents.msi" up to
In my investigation I have found that if you have seldom changing
thirdparty components... give them their own msi's and tie down there
version/product code. The boostrapper that the thirdparty msi of the
required version is already installed and doesn't seem to download or
install it.
-Raj
On
6 matches
Mail list logo
