Scratch that - there is already bug on this:
http://sourceforge.net/p/wix/bugs/3109/
-Original Message-
From: Philip Patrick [mailto:patri...@varonis.com]
Sent: Sunday, June 16, 2013 18:31
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bootstrapper reboots automatically
Hi
I would start trying to use 3 different upgrade codes and using Upgrade table
to prevent installation of "lower" versions of the product. My concert in this
approach - not sure if upgrade from Lite to Basic to Premium will work smoothly
- just need to find it out empirically.
If it won't work -
Hi,
I'm experiencing unwanted reboot when upgrading our product from one version to
another. This is seems an expected behavior, but I was not expecting it :) The
question - is there any way to prevent ANY reboot? Or maybe I can determine it
prior upgrade and prevent upgrade? Latter will work
Hyperlink control only available in Windows 2008 and Window 7. And the real
problem is that MSI simply fails on other systems if dialog has hyperlink. See
more info here:
http://www.installsite.org/pages/en/msi/articles/careful-with-that-hyperlink-on-your-msi-dialog/index.htm
-Original Mess
sss
Can please send me how u creating custom action
-Original Message-
From: Philip Patrick [mailto:patri...@varonis.com]
Sent: 03 January 2013 13:17
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Read System IP adresss
For such tasks I usually create
For such tasks I usually create a custom action that runs before AppSearch
(make sure to place it into UI sequence and Execute sequence, depending on your
needs). It gathers all information and sets relevant properties, which can be
used during installation then.
-Original Message-
From
Here is an excellent tutorial on how to add new dialogs in Wix and other nifty
things:
http://wix.tramontana.co.hu/tutorial/user-interface/new-link-in-the-chain
-Original Message-
From: Jimmy Nilsson [mailto:jimmy.nils...@evry.com]
Sent: Thursday, December 20, 2012 14:04
To: wix-users@l
Well, not sure ours was the best solution, but what we did is a custom action
that literally moves all registry entries related to per-user package to
per-machine. That means from
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\SID-OF-USER
to UserData\S-1-5-18 (latter stores p
undle will finish whatever the last operation
was. If it was uninstall, the bundle will uninstall.
3. No, a reboot is required. After the reboot the bundle will end up in the
correct state.
On Tue, Nov 27, 2012 at 3:56 AM, Philip Patrick wrote:
> Hi,
>
> I have an MSI and a bundle (sta
there anything I can do to prevent this behavior? Workaround or
something? Maybe I can fiddle with REBOOT property and pass to MSI
"ReallySuppress"?
Thanks,
Philip Patrick.
~~~
Full burn log below
[061C:08C0][2012-11-27T12:10:08]: Burn v3.6.3303.0, Windows v
Another option is to find the path in registry, in the Installer key. You will
need to know the following information:
* Product Code (or Upgrade Code and then find all products installed for it)
* How to convert GUID to "compressed" Microsoft's format, which is used in
registry
* For which user
11 matches
Mail list logo