Re: [WiX-users] How to force to launch application in silent install mode?
If your MSI was installed via group policy, and you succeeded in launching your application, it is possible that no user would ever see it to know that it needed upgrading. You could try adding a custom action in your MSI that runs your upgrade-check and if there is a newer version you fail the installation with a message that there is a newer version. Or, you wait around (after quiet installations) until the user finally decides that they are going to use your application and then find out that there is a newer version. Of course, if they run an interactive installation, you could simply remove the checkbox, leave the property, and always launch then (since you know that there is a real user there) and alert the user to your upgrade when the product launches. -Original Message- From: little.forest [mailto:little.for...@ymail.com] Sent: Thursday, November 19, 2009 11:33 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How to force to launch application in silent install mode? Thanks Sascha. Rebooting doesn't fit our requirement. I've made a workaround in our bootstrapper to launch the app after silent installation. It's not nice as our MSI users won't have this functionality. But this seems the best we could do so far. From: Sascha Beaumont sascha.beaum...@gmail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wednesday, November 18, 2009 4:10:56 PM Subject: Re: [WiX-users] How to force to launch application in silent install mode? Best solution I've used in the past was to schedule a reboot, it really depends on your app and your deployment requirements as to what will work for you. On Thu, Nov 19, 2009 at 10:13 AM, little.forest little.for...@ymail.com wrote: Thanks Sascha. I see your points. It looks like there is no any other workarounds, correct? From: Sascha Beaumont sascha.beaum...@gmail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wednesday, November 18, 2009 2:35:26 PM Subject: Re: [WiX-users] How to force to launch application in silent install mode? Hi, With regards to the quicklaunch shortcut, the checkbox is just setting a property, no different to setting the property on the command line. The property is set when InstallExecuteSequence runs, and you most likely have a condition on your quicklaunch component that checks the property. With regards to launching the application, you're tying the launch to the Finish button in the InstallUiSequence rather than to something that happens during InstallExecuteSequence. The following page might help explain the sequence: http://blogs.msdn.com/rflaming/archive/2006/09/21/765452.aspx Sascha On Thu, Nov 19, 2009 at 6:00 AM, little.forest little.for...@ymail.com wrote: Thanks Sascha. It's good to know that the InstallUISequence is never executed in quite mode. But in another case, I set a property in command line argument, it seems working. I mean, we have a checkbox called Install Quick Launch shortcut. By default it's off. So the quick launch shortcut isn't created by default. In command line, I added this 'INSTALLQUICKLAUNCHSHORTCUT=1' in command line, then in quite installation, the quick launch shortcut was created. So it seems working. I wonder why the similar case for Launch application on the final page would be different? I thought it's supposed to work the same way as the quick launch shortcut, right? Let me know if you know the reason. By the way, the reason we need to launch the application in quite installation is because these: we have an auto-update mechanism. The idea is, the application will periodically check if there is any new build available in our provisioning server. If there is any new version, then ask the end user if she wants to download it and install it. If the end user says yes, then we'll download it and install it. After installation of the new version, we'd like to automatically launch the application, because the previous status of the application was in running state. This is just like when you update your browser like Firefox or Chrome. I think it's okay if the application isn't launched by default in quite mode. But by setting some kind of property, the application will be launched in quite mode. This will satisfy both the network admin scenario as what you mentioned, and our case. Anyways, since it's not supported, I'll think about if I can schedule this launching action in our bootstrapper - we have a bootstrapper for the installer. Thanks again. From: Sascha Beaumont sascha.beaum...@gmail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tuesday, November 17, 2009 8:06:13 PM Subject: Re: [WiX-users] How to force to launch application in silent install
Re: [WiX-users] How to force to launch application in silent install mode?
Thanks Sascha. Rebooting doesn't fit our requirement. I've made a workaround in our bootstrapper to launch the app after silent installation. It's not nice as our MSI users won't have this functionality. But this seems the best we could do so far. From: Sascha Beaumont sascha.beaum...@gmail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wednesday, November 18, 2009 4:10:56 PM Subject: Re: [WiX-users] How to force to launch application in silent install mode? Best solution I've used in the past was to schedule a reboot, it really depends on your app and your deployment requirements as to what will work for you. On Thu, Nov 19, 2009 at 10:13 AM, little.forest little.for...@ymail.com wrote: Thanks Sascha. I see your points. It looks like there is no any other workarounds, correct? From: Sascha Beaumont sascha.beaum...@gmail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wednesday, November 18, 2009 2:35:26 PM Subject: Re: [WiX-users] How to force to launch application in silent install mode? Hi, With regards to the quicklaunch shortcut, the checkbox is just setting a property, no different to setting the property on the command line. The property is set when InstallExecuteSequence runs, and you most likely have a condition on your quicklaunch component that checks the property. With regards to launching the application, you're tying the launch to the Finish button in the InstallUiSequence rather than to something that happens during InstallExecuteSequence. The following page might help explain the sequence: http://blogs.msdn.com/rflaming/archive/2006/09/21/765452.aspx Sascha On Thu, Nov 19, 2009 at 6:00 AM, little.forest little.for...@ymail.com wrote: Thanks Sascha. It's good to know that the InstallUISequence is never executed in quite mode. But in another case, I set a property in command line argument, it seems working. I mean, we have a checkbox called Install Quick Launch shortcut. By default it's off. So the quick launch shortcut isn't created by default. In command line, I added this 'INSTALLQUICKLAUNCHSHORTCUT=1' in command line, then in quite installation, the quick launch shortcut was created. So it seems working. I wonder why the similar case for Launch application on the final page would be different? I thought it's supposed to work the same way as the quick launch shortcut, right? Let me know if you know the reason. By the way, the reason we need to launch the application in quite installation is because these: we have an auto-update mechanism. The idea is, the application will periodically check if there is any new build available in our provisioning server. If there is any new version, then ask the end user if she wants to download it and install it. If the end user says yes, then we'll download it and install it. After installation of the new version, we'd like to automatically launch the application, because the previous status of the application was in running state. This is just like when you update your browser like Firefox or Chrome. I think it's okay if the application isn't launched by default in quite mode. But by setting some kind of property, the application will be launched in quite mode. This will satisfy both the network admin scenario as what you mentioned, and our case. Anyways, since it's not supported, I'll think about if I can schedule this launching action in our bootstrapper - we have a bootstrapper for the installer. Thanks again. From: Sascha Beaumont sascha.beaum...@gmail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tuesday, November 17, 2009 8:06:13 PM Subject: Re: [WiX-users] How to force to launch application in silent install mode? In quite mode, the InstallUISequence is never executed, so the checkbox doesn't even really exist (only the property related to the checkbox) The documentation shows how to tie in execution to when the user clicks the Finish button - this button never exists and is never pushed in a silent installation so the application will never launch. Launching an application automatically during a quiet installation sounds like a *really bad idea* - what if someone pushes out the installation via Group Policy? How does your application handle being executed under a system administrator account with no desktop to interact with? Your best bet is to schedule the application to launch at next login using the RunOnce registry key, and then forcing a reboot post-install. That way you can be certain the application will launch in a user context, rather than in an elevated context - even though the reboot may be an inconvenience at least you'll end up with a more
Re: [WiX-users] How to force to launch application in silent install mode?
Thanks Sascha. It's good to know that the InstallUISequence is never executed in quite mode. But in another case, I set a property in command line argument, it seems working. I mean, we have a checkbox called Install Quick Launch shortcut. By default it's off. So the quick launch shortcut isn't created by default. In command line, I added this 'INSTALLQUICKLAUNCHSHORTCUT=1' in command line, then in quite installation, the quick launch shortcut was created. So it seems working. I wonder why the similar case for Launch application on the final page would be different? I thought it's supposed to work the same way as the quick launch shortcut, right? Let me know if you know the reason. By the way, the reason we need to launch the application in quite installation is because these: we have an auto-update mechanism. The idea is, the application will periodically check if there is any new build available in our provisioning server. If there is any new version, then ask the end user if she wants to download it and install it. If the end user says yes, then we'll download it and install it. After installation of the new version, we'd like to automatically launch the application, because the previous status of the application was in running state. This is just like when you update your browser like Firefox or Chrome. I think it's okay if the application isn't launched by default in quite mode. But by setting some kind of property, the application will be launched in quite mode. This will satisfy both the network admin scenario as what you mentioned, and our case. Anyways, since it's not supported, I'll think about if I can schedule this launching action in our bootstrapper - we have a bootstrapper for the installer. Thanks again. From: Sascha Beaumont sascha.beaum...@gmail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tuesday, November 17, 2009 8:06:13 PM Subject: Re: [WiX-users] How to force to launch application in silent install mode? In quite mode, the InstallUISequence is never executed, so the checkbox doesn't even really exist (only the property related to the checkbox) The documentation shows how to tie in execution to when the user clicks the Finish button - this button never exists and is never pushed in a silent installation so the application will never launch. Launching an application automatically during a quiet installation sounds like a *really bad idea* - what if someone pushes out the installation via Group Policy? How does your application handle being executed under a system administrator account with no desktop to interact with? Your best bet is to schedule the application to launch at next login using the RunOnce registry key, and then forcing a reboot post-install. That way you can be certain the application will launch in a user context, rather than in an elevated context - even though the reboot may be an inconvenience at least you'll end up with a more reliable setup thats isn't dependent on how the user chooses to install (command line, elevated, non-elevated, group policy, quiet, interactive, etc). Sascha On Wed, Nov 18, 2009 at 12:50 PM, little.forest little.for...@ymail.com wrote: In our code, we have this: Property Id=WIXUI_EXITDIALOGOPTIONALCHECKBOX Value=1 / So the checkbox is checked by default. I thought that means launch the application by default. But the application was not launched in quite(silent) mode: msiexec /i myapp.msi /qr I then tried to set property in command line, it didn't work either: msiexec /i myapp.msi WIXUI_EXITDIALOGOPTIONALCHECKBOX=1 /qr Do you know how to automatically launch the application in quiet(silent) mode? Thanks. From: little.forest little.for...@ymail.com To: wix-users@lists.sourceforge.net Sent: Tuesday, November 17, 2009 2:20:58 PM Subject: [WiX-users] How to force to launch application in silent install mode? I'd like to know how to force to launch the application in silent install mode. I thought this would work: msiexec /i myapp.msi WIXUI_EXITDIALOGOPTIONALCHECKBOX=1 /qr But after installation, the application wasn't launched. By the way, we use the 'standard' way from Wix.chm(How To: Run the Installed Application After Setup) for the 'launch application'. How can I make the application run anyways after a silent installation? By the way, from the log, the CustomAction LaunchApplication never run. I don't know why it didn't run. Thanks. /Brian __ Make your browsing faster, safer, and easier with the new Internet Explorer® 8. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/ -- Let Crystal Reports handle the reporting - Free Crystal Reports
Re: [WiX-users] How to force to launch application in silent install mode?
If you happens to know how to launch the application in quite(silent) mode, please let me know. Thanks. From: little.forest little.for...@ymail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wednesday, November 18, 2009 11:00:16 AM Subject: Re: [WiX-users] How to force to launch application in silent install mode? Thanks Sascha. It's good to know that the InstallUISequence is never executed in quite mode. But in another case, I set a property in command line argument, it seems working. I mean, we have a checkbox called Install Quick Launch shortcut. By default it's off. So the quick launch shortcut isn't created by default. In command line, I added this 'INSTALLQUICKLAUNCHSHORTCUT=1' in command line, then in quite installation, the quick launch shortcut was created. So it seems working. I wonder why the similar case for Launch application on the final page would be different? I thought it's supposed to work the same way as the quick launch shortcut, right? Let me know if you know the reason. By the way, the reason we need to launch the application in quite installation is because these: we have an auto-update mechanism. The idea is, the application will periodically check if there is any new build available in our provisioning server. If there is any new version, then ask the end user if she wants to download it and install it. If the end user says yes, then we'll download it and install it. After installation of the new version, we'd like to automatically launch the application, because the previous status of the application was in running state. This is just like when you update your browser like Firefox or Chrome. I think it's okay if the application isn't launched by default in quite mode. But by setting some kind of property, the application will be launched in quite mode. This will satisfy both the network admin scenario as what you mentioned, and our case. Anyways, since it's not supported, I'll think about if I can schedule this launching action in our bootstrapper - we have a bootstrapper for the installer. Thanks again. From: Sascha Beaumont sascha.beaum...@gmail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tuesday, November 17, 2009 8:06:13 PM Subject: Re: [WiX-users] How to force to launch application in silent install mode? In quite mode, the InstallUISequence is never executed, so the checkbox doesn't even really exist (only the property related to the checkbox) The documentation shows how to tie in execution to when the user clicks the Finish button - this button never exists and is never pushed in a silent installation so the application will never launch. Launching an application automatically during a quiet installation sounds like a *really bad idea* - what if someone pushes out the installation via Group Policy? How does your application handle being executed under a system administrator account with no desktop to interact with? Your best bet is to schedule the application to launch at next login using the RunOnce registry key, and then forcing a reboot post-install. That way you can be certain the application will launch in a user context, rather than in an elevated context - even though the reboot may be an inconvenience at least you'll end up with a more reliable setup thats isn't dependent on how the user chooses to install (command line, elevated, non-elevated, group policy, quiet, interactive, etc). Sascha On Wed, Nov 18, 2009 at 12:50 PM, little.forest little.for...@ymail.com wrote: In our code, we have this: Property Id=WIXUI_EXITDIALOGOPTIONALCHECKBOX Value=1 / So the checkbox is checked by default. I thought that means launch the application by default. But the application was not launched in quite(silent) mode: msiexec /i myapp.msi /qr I then tried to set property in command line, it didn't work either: msiexec /i myapp.msi WIXUI_EXITDIALOGOPTIONALCHECKBOX=1 /qr Do you know how to automatically launch the application in quiet(silent) mode? Thanks. From: little.forest little.for...@ymail.com To: wix-users@lists.sourceforge.net Sent: Tuesday, November 17, 2009 2:20:58 PM Subject: [WiX-users] How to force to launch application in silent install mode? I'd like to know how to force to launch the application in silent install mode. I thought this would work: msiexec /i myapp.msi WIXUI_EXITDIALOGOPTIONALCHECKBOX=1 /qr But after installation, the application wasn't launched. By the way, we use the 'standard' way from Wix.chm(How To: Run the Installed Application After Setup) for the 'launch application'. How can I make the application run anyways after a silent installation? By the way, from the log, the CustomAction LaunchApplication never run. I don't know why it didn't run.
Re: [WiX-users] How to force to launch application in silent install mode?
Hi, With regards to the quicklaunch shortcut, the checkbox is just setting a property, no different to setting the property on the command line. The property is set when InstallExecuteSequence runs, and you most likely have a condition on your quicklaunch component that checks the property. With regards to launching the application, you're tying the launch to the Finish button in the InstallUiSequence rather than to something that happens during InstallExecuteSequence. The following page might help explain the sequence: http://blogs.msdn.com/rflaming/archive/2006/09/21/765452.aspx Sascha On Thu, Nov 19, 2009 at 6:00 AM, little.forest little.for...@ymail.com wrote: Thanks Sascha. It's good to know that the InstallUISequence is never executed in quite mode. But in another case, I set a property in command line argument, it seems working. I mean, we have a checkbox called Install Quick Launch shortcut. By default it's off. So the quick launch shortcut isn't created by default. In command line, I added this 'INSTALLQUICKLAUNCHSHORTCUT=1' in command line, then in quite installation, the quick launch shortcut was created. So it seems working. I wonder why the similar case for Launch application on the final page would be different? I thought it's supposed to work the same way as the quick launch shortcut, right? Let me know if you know the reason. By the way, the reason we need to launch the application in quite installation is because these: we have an auto-update mechanism. The idea is, the application will periodically check if there is any new build available in our provisioning server. If there is any new version, then ask the end user if she wants to download it and install it. If the end user says yes, then we'll download it and install it. After installation of the new version, we'd like to automatically launch the application, because the previous status of the application was in running state. This is just like when you update your browser like Firefox or Chrome. I think it's okay if the application isn't launched by default in quite mode. But by setting some kind of property, the application will be launched in quite mode. This will satisfy both the network admin scenario as what you mentioned, and our case. Anyways, since it's not supported, I'll think about if I can schedule this launching action in our bootstrapper - we have a bootstrapper for the installer. Thanks again. From: Sascha Beaumont sascha.beaum...@gmail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tuesday, November 17, 2009 8:06:13 PM Subject: Re: [WiX-users] How to force to launch application in silent install mode? In quite mode, the InstallUISequence is never executed, so the checkbox doesn't even really exist (only the property related to the checkbox) The documentation shows how to tie in execution to when the user clicks the Finish button - this button never exists and is never pushed in a silent installation so the application will never launch. Launching an application automatically during a quiet installation sounds like a *really bad idea* - what if someone pushes out the installation via Group Policy? How does your application handle being executed under a system administrator account with no desktop to interact with? Your best bet is to schedule the application to launch at next login using the RunOnce registry key, and then forcing a reboot post-install. That way you can be certain the application will launch in a user context, rather than in an elevated context - even though the reboot may be an inconvenience at least you'll end up with a more reliable setup thats isn't dependent on how the user chooses to install (command line, elevated, non-elevated, group policy, quiet, interactive, etc). Sascha On Wed, Nov 18, 2009 at 12:50 PM, little.forest little.for...@ymail.com wrote: In our code, we have this: Property Id=WIXUI_EXITDIALOGOPTIONALCHECKBOX Value=1 / So the checkbox is checked by default. I thought that means launch the application by default. But the application was not launched in quite(silent) mode: msiexec /i myapp.msi /qr I then tried to set property in command line, it didn't work either: msiexec /i myapp.msi WIXUI_EXITDIALOGOPTIONALCHECKBOX=1 /qr Do you know how to automatically launch the application in quiet(silent) mode? Thanks. From: little.forest little.for...@ymail.com To: wix-users@lists.sourceforge.net Sent: Tuesday, November 17, 2009 2:20:58 PM Subject: [WiX-users] How to force to launch application in silent install mode? I'd like to know how to force to launch the application in silent install mode. I thought this would work: msiexec /i myapp.msi WIXUI_EXITDIALOGOPTIONALCHECKBOX=1 /qr But after installation, the application wasn't
Re: [WiX-users] How to force to launch application in silent install mode?
Thanks Sascha. I see your points. It looks like there is no any other workarounds, correct? From: Sascha Beaumont sascha.beaum...@gmail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wednesday, November 18, 2009 2:35:26 PM Subject: Re: [WiX-users] How to force to launch application in silent install mode? Hi, With regards to the quicklaunch shortcut, the checkbox is just setting a property, no different to setting the property on the command line. The property is set when InstallExecuteSequence runs, and you most likely have a condition on your quicklaunch component that checks the property. With regards to launching the application, you're tying the launch to the Finish button in the InstallUiSequence rather than to something that happens during InstallExecuteSequence. The following page might help explain the sequence: http://blogs.msdn.com/rflaming/archive/2006/09/21/765452.aspx Sascha On Thu, Nov 19, 2009 at 6:00 AM, little.forest little.for...@ymail.com wrote: Thanks Sascha. It's good to know that the InstallUISequence is never executed in quite mode. But in another case, I set a property in command line argument, it seems working. I mean, we have a checkbox called Install Quick Launch shortcut. By default it's off. So the quick launch shortcut isn't created by default. In command line, I added this 'INSTALLQUICKLAUNCHSHORTCUT=1' in command line, then in quite installation, the quick launch shortcut was created. So it seems working. I wonder why the similar case for Launch application on the final page would be different? I thought it's supposed to work the same way as the quick launch shortcut, right? Let me know if you know the reason. By the way, the reason we need to launch the application in quite installation is because these: we have an auto-update mechanism. The idea is, the application will periodically check if there is any new build available in our provisioning server. If there is any new version, then ask the end user if she wants to download it and install it. If the end user says yes, then we'll download it and install it. After installation of the new version, we'd like to automatically launch the application, because the previous status of the application was in running state. This is just like when you update your browser like Firefox or Chrome. I think it's okay if the application isn't launched by default in quite mode. But by setting some kind of property, the application will be launched in quite mode. This will satisfy both the network admin scenario as what you mentioned, and our case. Anyways, since it's not supported, I'll think about if I can schedule this launching action in our bootstrapper - we have a bootstrapper for the installer. Thanks again. From: Sascha Beaumont sascha.beaum...@gmail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tuesday, November 17, 2009 8:06:13 PM Subject: Re: [WiX-users] How to force to launch application in silent install mode? In quite mode, the InstallUISequence is never executed, so the checkbox doesn't even really exist (only the property related to the checkbox) The documentation shows how to tie in execution to when the user clicks the Finish button - this button never exists and is never pushed in a silent installation so the application will never launch. Launching an application automatically during a quiet installation sounds like a *really bad idea* - what if someone pushes out the installation via Group Policy? How does your application handle being executed under a system administrator account with no desktop to interact with? Your best bet is to schedule the application to launch at next login using the RunOnce registry key, and then forcing a reboot post-install. That way you can be certain the application will launch in a user context, rather than in an elevated context - even though the reboot may be an inconvenience at least you'll end up with a more reliable setup thats isn't dependent on how the user chooses to install (command line, elevated, non-elevated, group policy, quiet, interactive, etc). Sascha On Wed, Nov 18, 2009 at 12:50 PM, little.forest little.for...@ymail.com wrote: In our code, we have this: Property Id=WIXUI_EXITDIALOGOPTIONALCHECKBOX Value=1 / So the checkbox is checked by default. I thought that means launch the application by default. But the application was not launched in quite(silent) mode: msiexec /i myapp.msi /qr I then tried to set property in command line, it didn't work either: msiexec /i myapp.msi WIXUI_EXITDIALOGOPTIONALCHECKBOX=1 /qr Do you know how to automatically launch the application in quiet(silent) mode? Thanks. From: little.forest
Re: [WiX-users] How to force to launch application in silent install mode?
Best solution I've used in the past was to schedule a reboot, it really depends on your app and your deployment requirements as to what will work for you. On Thu, Nov 19, 2009 at 10:13 AM, little.forest little.for...@ymail.com wrote: Thanks Sascha. I see your points. It looks like there is no any other workarounds, correct? From: Sascha Beaumont sascha.beaum...@gmail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Wednesday, November 18, 2009 2:35:26 PM Subject: Re: [WiX-users] How to force to launch application in silent install mode? Hi, With regards to the quicklaunch shortcut, the checkbox is just setting a property, no different to setting the property on the command line. The property is set when InstallExecuteSequence runs, and you most likely have a condition on your quicklaunch component that checks the property. With regards to launching the application, you're tying the launch to the Finish button in the InstallUiSequence rather than to something that happens during InstallExecuteSequence. The following page might help explain the sequence: http://blogs.msdn.com/rflaming/archive/2006/09/21/765452.aspx Sascha On Thu, Nov 19, 2009 at 6:00 AM, little.forest little.for...@ymail.com wrote: Thanks Sascha. It's good to know that the InstallUISequence is never executed in quite mode. But in another case, I set a property in command line argument, it seems working. I mean, we have a checkbox called Install Quick Launch shortcut. By default it's off. So the quick launch shortcut isn't created by default. In command line, I added this 'INSTALLQUICKLAUNCHSHORTCUT=1' in command line, then in quite installation, the quick launch shortcut was created. So it seems working. I wonder why the similar case for Launch application on the final page would be different? I thought it's supposed to work the same way as the quick launch shortcut, right? Let me know if you know the reason. By the way, the reason we need to launch the application in quite installation is because these: we have an auto-update mechanism. The idea is, the application will periodically check if there is any new build available in our provisioning server. If there is any new version, then ask the end user if she wants to download it and install it. If the end user says yes, then we'll download it and install it. After installation of the new version, we'd like to automatically launch the application, because the previous status of the application was in running state. This is just like when you update your browser like Firefox or Chrome. I think it's okay if the application isn't launched by default in quite mode. But by setting some kind of property, the application will be launched in quite mode. This will satisfy both the network admin scenario as what you mentioned, and our case. Anyways, since it's not supported, I'll think about if I can schedule this launching action in our bootstrapper - we have a bootstrapper for the installer. Thanks again. From: Sascha Beaumont sascha.beaum...@gmail.com To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Sent: Tuesday, November 17, 2009 8:06:13 PM Subject: Re: [WiX-users] How to force to launch application in silent install mode? In quite mode, the InstallUISequence is never executed, so the checkbox doesn't even really exist (only the property related to the checkbox) The documentation shows how to tie in execution to when the user clicks the Finish button - this button never exists and is never pushed in a silent installation so the application will never launch. Launching an application automatically during a quiet installation sounds like a *really bad idea* - what if someone pushes out the installation via Group Policy? How does your application handle being executed under a system administrator account with no desktop to interact with? Your best bet is to schedule the application to launch at next login using the RunOnce registry key, and then forcing a reboot post-install. That way you can be certain the application will launch in a user context, rather than in an elevated context - even though the reboot may be an inconvenience at least you'll end up with a more reliable setup thats isn't dependent on how the user chooses to install (command line, elevated, non-elevated, group policy, quiet, interactive, etc). Sascha On Wed, Nov 18, 2009 at 12:50 PM, little.forest little.for...@ymail.com wrote: In our code, we have this: Property Id=WIXUI_EXITDIALOGOPTIONALCHECKBOX Value=1 / So the checkbox is checked by default. I thought that means launch the application by default. But the application was not launched in quite(silent) mode: msiexec /i myapp.msi /qr I then tried to set property in
[WiX-users] How to force to launch application in silent install mode?
I'd like to know how to force to launch the application in silent install mode. I thought this would work: msiexec /i myapp.msi WIXUI_EXITDIALOGOPTIONALCHECKBOX=1 /qr But after installation, the application wasn't launched. By the way, we use the 'standard' way from Wix.chm(How To: Run the Installed Application After Setup) for the 'launch application'. How can I make the application run anyways after a silent installation? By the way, from the log, the CustomAction LaunchApplication never run. I don't know why it didn't run. Thanks. /Brian __ Make your browsing faster, safer, and easier with the new Internet Explorer® 8. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to force to launch application in silent install mode?
In our code, we have this: Property Id=WIXUI_EXITDIALOGOPTIONALCHECKBOX Value=1 / So the checkbox is checked by default. I thought that means launch the application by default. But the application was not launched in quite(silent) mode: msiexec /i myapp.msi /qr I then tried to set property in command line, it didn't work either: msiexec /i myapp.msi WIXUI_EXITDIALOGOPTIONALCHECKBOX=1 /qr Do you know how to automatically launch the application in quiet(silent) mode? Thanks. From: little.forest little.for...@ymail.com To: wix-users@lists.sourceforge.net Sent: Tuesday, November 17, 2009 2:20:58 PM Subject: [WiX-users] How to force to launch application in silent install mode? I'd like to know how to force to launch the application in silent install mode. I thought this would work: msiexec /i myapp.msi WIXUI_EXITDIALOGOPTIONALCHECKBOX=1 /qr But after installation, the application wasn't launched. By the way, we use the 'standard' way from Wix.chm(How To: Run the Installed Application After Setup) for the 'launch application'. How can I make the application run anyways after a silent installation? By the way, from the log, the CustomAction LaunchApplication never run. I don't know why it didn't run. Thanks. /Brian __ Make your browsing faster, safer, and easier with the new Internet Explorer® 8. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to force to launch application in silent install mode?
In quite mode, the InstallUISequence is never executed, so the checkbox doesn't even really exist (only the property related to the checkbox) The documentation shows how to tie in execution to when the user clicks the Finish button - this button never exists and is never pushed in a silent installation so the application will never launch. Launching an application automatically during a quiet installation sounds like a *really bad idea* - what if someone pushes out the installation via Group Policy? How does your application handle being executed under a system administrator account with no desktop to interact with? Your best bet is to schedule the application to launch at next login using the RunOnce registry key, and then forcing a reboot post-install. That way you can be certain the application will launch in a user context, rather than in an elevated context - even though the reboot may be an inconvenience at least you'll end up with a more reliable setup thats isn't dependent on how the user chooses to install (command line, elevated, non-elevated, group policy, quiet, interactive, etc). Sascha On Wed, Nov 18, 2009 at 12:50 PM, little.forest little.for...@ymail.com wrote: In our code, we have this: Property Id=WIXUI_EXITDIALOGOPTIONALCHECKBOX Value=1 / So the checkbox is checked by default. I thought that means launch the application by default. But the application was not launched in quite(silent) mode: msiexec /i myapp.msi /qr I then tried to set property in command line, it didn't work either: msiexec /i myapp.msi WIXUI_EXITDIALOGOPTIONALCHECKBOX=1 /qr Do you know how to automatically launch the application in quiet(silent) mode? Thanks. From: little.forest little.for...@ymail.com To: wix-users@lists.sourceforge.net Sent: Tuesday, November 17, 2009 2:20:58 PM Subject: [WiX-users] How to force to launch application in silent install mode? I'd like to know how to force to launch the application in silent install mode. I thought this would work: msiexec /i myapp.msi WIXUI_EXITDIALOGOPTIONALCHECKBOX=1 /qr But after installation, the application wasn't launched. By the way, we use the 'standard' way from Wix.chm(How To: Run the Installed Application After Setup) for the 'launch application'. How can I make the application run anyways after a silent installation? By the way, from the log, the CustomAction LaunchApplication never run. I don't know why it didn't run. Thanks. /Brian __ Make your browsing faster, safer, and easier with the new Internet Explorer® 8. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users __ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
