MSI SDK has a list of reasons why SelfReg is "evil".
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jeff sacksteder
Sent: Tuesday, June 17, 2008 18:02
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] self-registering
I'm tryi
> I'm trying to package a legacy program that registers some third-party
> ocx and dlls. I see that the consensus is that I should be handling
> this with a registry component. However, this application's
> 'installer' just copies stuff into a folder off the root of c:\ and
> runs a 'register.b
I'm trying to package a legacy program that registers some third-party
ocx and dlls. I see that the consensus is that I should be handling
this with a registry component. However, this application's
'installer' just copies stuff into a folder off the root of c:\ and
runs a 'register.bat' to regsvr3
The best solution is to extract the information with tallow or heat and specify
the correct table
entries. Try to avoid selfreg where possible.
Rob
[EMAIL PROTECTED] wrote:
> hi all,
>
> i have to register a dll inside my msi. i've seen that the table selfreg can
> do
> that BUT i've also se
hi all,
i have to register a dll inside my msi. i've seen that the table selfreg can do
that BUT i've also seen another method by using customaction calling msiexec /y
to reg (and /z to unreg).
what is the better solution?
thanks in advance
--
---
5 matches
Mail list logo