Im sorry i dont quite understand what you are suggesting. If i remove the RUNFROMEXE the user can launch the msi without the exe. which is not what i want. And .Net is not my only prerequisite.. i have over 10 custom prerequisite.. which i have working perfectly. my only issue is modifying the setup.exe generated by GenerateBootStrapper to pass this parameter along with some upgrading parameters to the msiexec call when it launches the msi.
Dominik Guder wrote: > > > conkerjoe wrote: >> >> the first being, i do not want the user to launch the msi standalone, >> this is easy, now the MSI is expecting a parameter RUNFROMEXE=1 before it >> will run. my issue is i cannot get the setup.exe to pass this to the msi >> when launching it. >> > > Hi, > > I couldn't find any way to provide RUNFROMEXE from Setup.exe. Besides this > RUNFROMEXE=1 could be added to command line of msiexec too. > > What I would try is to do the prerequesites check within the msi again > (and remove RUNFROMEXE). With an appropriate message to use setup.exe > instead of msi when the condition fails. > See: http://www.wixwiki.com/index.php?title=NetFxExtension > > hth > > Dominik > > -- View this message in context: http://www.nabble.com/Frustrating-Bootstrapper-problem-tf4435226.html#a12654902 Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
