See below.
From: Ricardo Lopes [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 21, 2007 9:36 AM
To: Dan Hoeger
Cc: John Vottero; wix-users@lists.sourceforge.net
Subject: Re: Re: [WiX-users] Prevent MSI to be invoked directly
[John] I didn't know about the IExpress, looks nice, shouldn't be a problem to
automate the process in my build server using the SED file.
[Dan] that was more what i was thinking, do you know how can i pass a param to
the installer using the msbuild GenerateBootstrapper task? i tried to use "
msifile.msi DIRECTEXECUTE=1" on the ApplicationFile but it throws an error when
launching the msi, he thinks the params are part of the filename. Any ideas ?
Our bootstrapper exe that we use launches MSIEXEC so we just have to add this
to the command line.
[Dan] Are the REMOVE, REINSTALL, PATCH conditions there to allow calling from
the control panel add/remove programs?
Yes
Thanks.
On 21/02/07, Dan Hoeger < [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:
Here is what we use:
<Condition Message="Installation may not be executed directly. Please run
Setup.exe in root folder of installation disk">DIRECTEXECUTE = 1 OR REMOVE =
"ALL" OR REINSTALL="ALL" OR PATCH OR MSIPATCHREMOVE</Condition>
Then from your bootstrapper you need to add DIRECTEXECUTE=1 to the command line
Thanks,
Dan
From: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> [mailto:[EMAIL
PROTECTED]<mailto:[EMAIL PROTECTED]>] On Behalf Of John Vottero
Sent: Wednesday, February 21, 2007 9:03 AM
To: Ricardo Lopes;
wix-users@lists.sourceforge.net<mailto:wix-users@lists.sourceforge.net>
Subject: Re: [WiX-users] Prevent MSI to be invoked directly
We use Wix and the MSBuild GenerateBootstrapper too. We use IExpress.exe to to
combine everything into a single executable. IExpress is part of IE so, you
probably already have it.
________________________________
From: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> [mailto:[EMAIL
PROTECTED]<mailto:[EMAIL PROTECTED]>] On Behalf Of Ricardo Lopes
Sent: Wednesday, February 21, 2007 5:00 AM
To: wix-users@lists.sourceforge.net<mailto:wix-users@lists.sourceforge.net>
Subject: [WiX-users] Prevent MSI to be invoked directly
Hi,
I made a MSI installer using Wix and a bootstrapper using the msbuild
GenerateBootstrapper task, it creates a setup.exe and a msi file, but the msi
can be invoke directly overcoming the checks made by the bootstrapper and there
are checks on the bootstrapper that are difficult to include as conditions to
prevent the installer from running.
Is there any way to do any of this :
- avoid the msi from unless is started by the bootstrapper (some kind of
condition)
- merge the bootstrapper and the msi in only one file and start the setup.exe
when the merged file is started.
- any other suggestion ?
I tried to change the extension of the msi to .dat and start that file from the
setup.exe but it doesn't work as i expected.
Thanks,
Ricardo Lopes.
--
Ricardo Lopes
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
