On 2013-06-25 5:23, Bob Arnson wrote:
> On 24-Jun-13 14:17, Lukas Haase wrote:
>>
> Custom actions after InstallFinalize cannot run elevated.
Thank you. What would be the best place to include this CA and ensure
that it runs ele
Hi,
I have a custom action in a DLL. If I check admin rights in the DLL with
IsUserAnAdmin it returns FALSE!
The wxs file makes sure that installation can only run with admin privs:
Privileged
The custom action is included via:
NOT
Installed
The UpdateInstall.dll exports UpdateInstal
Hi,
For my application, I use software activation. However, in case they
activation fails, the software should work for 14 days after
installation (grace period).
While I know it is difficult to protect this it should at least not be
circumvented by simple re-installation.
What is the best proce
Hi,
Am 17.02.2011 02:07, schrieb Bob Arnson:
> On 16-Feb-11 17:13, Lukas Haase wrote:
>> However, what happens when program with same UpgradeCode is first
>> installed globally as administrator and the next version installed as
>> non-admin user?
>
> MSI doesn'
Hi,
How is it handled when I do not check for admin rights and users install
my program without admin privileges?
In this case, they won't be able to register the program in the global
Uninstall list/MSI registry I guess.
However, what happens when program with same UpgradeCode is first
insta
e section and to schedule RemoveExistingProducts,
> there is an example here:
> http://neilsleightholm.blogspot.com/2009/01/wix-script-for-major-upgrade
> s.html
>
> Neil
>
> -Original Message-
> From: Lukas Haase [mailto:lukasha...@gmx.at]
> Sent: 03 August 2010
Hi,
It was mentioned a few times on this list that if the UpgradeCode stays
the same, MSI performes an upgrade.
This is my preamble:
The upgradecode is defined successfully with http://p.sf.net/sfu/dev2dev-palm
___
WiX-users mailing list
W
Hi,
I looked at the docs at
http://msdn.microsoft.com/en-us/library/aa368250%28VS.85%29.aspx but I
could not find any information:
Within a DLL extension for MSI, how can I found out ...
a) In which UI mode I am (full, reduced, simple, no)
b) If I am called in InstallUISequence or InstallExecu
Hi,
As written in some other posts I have written A DLL for MSI which
detects my old setup program, asks the user if he wants to deinstall and
deinstalls the old product.
However, the old setup application does not offer a silent uninstall.
Right now, I call the DLL after LaunchConditions in *
Am 28.07.2010 19:09, schrieb Blair:
> #2: Add the InstallScope="perMachine" attribute to your Package element.
> This will add the ALLUSERS property for you.
Is there an advantage/disadvantage about
1
?
Regards
Luke
--
linked each set of WIXOUTs into MSIs, as you
> mention. I don't see a problem with that.
>
> Not every build environment easily supports that approach, so you need to do
> what works for your build system.
>
> -Original Message-
> From: Lukas Haase [mailto:lukasha...@
for an installation :)
>
> !ERROR_SUCCESS isnt a valid custom action return. See this list
> http://msdn.microsoft.com/en-us/library/aa368072%28VS.85%29.aspx
>
>
> -Original Message-
> From: Lukas Haase [mailto:lukasha...@gmx.at]
> Sent: 26 July 2010 11:44
> To: wix-users@li
he command-line (since it is a public property)). If
> you follow 3.3 AND 3.4, you will have that double-check running.
>
> -Original Message-
> From: Lukas Haase [mailto:lukasha...@gmx.at]
> Sent: Sunday, July 25, 2010 5:01 AM
> To: wix-users@lists.sourceforge.net
Dear Bob,
Am 25.07.2010 15:45, schrieb Bob Arnson:
> On 7/25/2010 8:10 AM, Lukas Haase wrote:
>> However, there is also need to replace Product/@Id and
>> Product/@UpgradeCode ...
>
> Use preprocessor variables and/or localization variables.
Thank you for your reply. This
r upgrade
> (some convenience properties here:
> http://code.dblock.org/ShowPost.aspx?id=42). It was pretty hard overall and
> took more effort to clean-up once the customers were off those very old
> versions.
>
> dB. @ dblock.org
> Moscow|Geneva|Seattle|New York
>
>
> -O
gt; If the other setup package is not-at-all MSI, there is nothing to pass to
> Windows Installer, since WI can only deal with MSI packages, and you will
> need to execute the uninstall executable somehow/somewhere.
>
> -Original Message-
> From: Lukas Haase [mailto:lukasha...@gm
box from a custom action (and the only
> supported way if you must do so from the execute sequence) is using the
> MsiProcessMessage API (or something that wraps it, like WcaProcessMessage or
> Microsoft.Deployment.WindowsInstaller.Session.Message).
>
> -Original Message-
design is you need a chainer to manage the
> install/unistall/update process.
>
> On Thu, Jul 22, 2010 at 12:37 PM, Lukas Haase wrote:
>
>> Thank you everybody for the discussion!
>>
>> The result is clear to me: I won't use minor- and small updates.
>>
>
appreciated!
Regards,
Luke
[1] http://www.tramontana.co.hu/wix/lesson3.php#3.1
[2]
http://www.tramontana.co.hu/wix/download.php?file=samples/sampleca.zip&type=application/zip
Am 23.07.2010 14:18, schrieb Lukas Haase:
> Dear Pally,
>
> Am 23.07.2010 11:04, schrieb Pally Sandhe
Dear Pally,
Am 23.07.2010 11:04, schrieb Pally Sandher:
> MSI (c) (74:80) [21:07:26:477]: Doing action: ValidateProductID Aktion
> 21:07:26: ValidateProductID.
>
> That's the InstallUISequence not the InstallExecuteSequence.
Indeed! I changed now to InstallUISequence and now it works!
But why?
E in the
> MSI (use ORCA to see what got into the MSI)?
>
> -Original Message-----
> From: Lukas Haase [mailto:lukasha...@gmx.at]
> Sent: Thursday, July 22, 2010 12:12 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] InstallExecuteSequence completely ignored
&
erbose log file will show you at the top.
>
> On Thu, Jul 22, 2010 at 12:12 PM, Lukas Haase wrote:
>
>> Hi,
>>
>> As proposed in one mail I wrote a DLL for detecting old installations.
>> But WiX seems to completely ignore InstallExecuteSequence!
>>
>>
Dear Blair,
Am 22.07.2010 01:04, schrieb Blair:
> 1. You can build MSIs with WiX that don't require running the setup as
> administrator. Nothing that can be done outside of Windows Installer without
> elevation requires elevation in Windows Installer to also do.
In fact this is exactly what I do
h-style wrappers (zip-exe
>>> style)
>>> for their MSI distribution.
>>>
>>> -Original Message-
>>> From: Christopher Painter [mailto:chr...@deploymentengineering.com]
>>> Sent: Wednesday, July 21, 2010 2:51 PM
>>> To: Gen
door). Of course, the savings using
> patching goes up the more you don't change, so my "back-of-the-envelope"
> analysis may not be correct.
>
> Blair
>
> -Original Message-
> From: Lukas Haase [mailto:lukasha...@gmx.at]
> Sent: Thursday, July 22, 2010 4:49 AM
&
Hi,
As proposed in one mail I wrote a DLL for detecting old installations.
But WiX seems to completely ignore InstallExecuteSequence!
I played around, tried different things but it is just ignored!
For testing I just added this to my file:
Notepad.exe
Even if I install with msiexec /i
r=... ...
And for the second problem (TARGETDIR/INSTALLDIR) there is another
"hidden" switch:
heat ... -var var.PdfFolder=... -dr INSTALLDIR ...
Regards,
Luke
[1] http://wix.sourceforge.net/manual-wix3/heat.htm
> -Original Message-
> From: Lukas Haase [mailto:luk
is what you mean?
OriginalDatabase ~<> "\MYSUPPORTEDFILENAME.msi"
Regards,
Luke
> Christopher Painter, Author of Deployment Engineering Blog
> Have a hot tip, know a secret or read a really good thread that deserves
> attention? E-Mail Me
>
>
>
> - Original Message --
Am 22.07.2010 00:07, schrieb Lukas Haase:
> Dear Blair,
>
> I do not fully understand. You mean the -ag switch?
>
> But then on every compile the PDF files get a different GUID, don't
> they? Then back to the original question: Does it matter in ANY way if
> they get a
quot;*") and you should setup a component group for your PDF
> files (then you can simply refer to them from your feature using the
> ComponentGroupRef element).
>
> -----Original Message-
> From: Lukas Haase [mailto:lukasha...@gmx.at]
> Sent: Wednesday, July 21, 2010 1:29 P
Hi,
Does the filename of the msi file matter in any way?
I really DO NOT hope so! Because I have no influence if the user renames
the file before installing?!
[1] says: "There are cases when the Windows Installer forces you to use
a major upgrade [...] You have to when you change the name of t
Dear Pally,
I have the same problem. BIG HINT for all users!
When you get
heat.exe : warning HEAT5150 : Could not harvest data from a file that
was expected to be a SelfReg
DLL: TestProtocol.dll. If this file does not support SelfReg you can
ignore this warning. Otherwise, this error detail may
Hi,
My setup project consists of a bunch of "static" files (application,
DLL), a huge databasefile and a vast amount of PDF files. The PDF files
are very volatile, they change from update to update (some are removed,
some are added but no of them are changed).
As they are many files I would re
Hi,
Today I began creating my first WiX project. Until now I used
SetupSpecialist but as I am facing serious problems with it I want to
use WiX in future.
This is my first big question: On clients' computers there will be an
old instance of my program (with SetupSpecialist) installed. Even wor
34 matches
Mail list logo
