Re: [WiX-users] Frustrating Bootstrapper problem
conkerjoe wrote: 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. Hi, I'm sorry to be not clear enough. I did another check and it looks like that the setup.exe generated by GenerateBootStrapper could not handle parameters for MSI. To be more clear I try to explain again: Right now you have one LaunchConditon checking RUNFROMEXE. My suggestion was to add one LaunchCondition for each of your Prerequisites. The properties for each condition could be filled per AppSearch (RegistrySearch or FileSearch) See http://www.tramontana.co.hu/wix/lesson3.php and don't forget to add LaunchConditions After='AppSearch' / as mentioned in tutorial So your msi is protected whether it is called directly or per bootstrapper. Alternatively you could give dotnetinstaller http://www.devage.com/ a try (see http://www.nabble.com/Downloading-and-launching-apps-during-install-t3651203.html ) hth Dominik -- View this message in context: http://www.nabble.com/Frustrating-Bootstrapper-problem-tf4435226.html#a12674138 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/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Frustrating Bootstrapper problem
I have a WIX Msi install almost working fully now. I also have the bootstrapper installing the prerequisites then launching the msi without a hitch this all works great. btw im using the GenerateBootStrapper task for msbuild to generate the bootstrapper, however i have 2 major issues left. 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. I have tried msistuff which appears to work, i view the properties of the exe, there are none, i run the msistuff command and check again and my parameters are there, i launch the setup.exe and it doesnt make any difference. Surely someone must be doing something similar and have solved the problem.. thanks in advance -- View this message in context: http://www.nabble.com/Frustrating-Bootstrapper-problem-tf4435226.html#a12653405 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/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Frustrating Bootstrapper problem
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#a12654892 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/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Frustrating Bootstrapper problem
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/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
