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
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:
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
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,
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
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,
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
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
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 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
10 matches
Mail list logo
