Hi Dan,
 
Did you ever receive an answer to this question?  I've been having a
similar difficulty and I didn't get much more from this mailing list
other than the suggestion to put the registry changes directly into the
WXS file (which has been the direction of my current investigation.)
 
I used:
 
<CustomAction Id="EXEREG_ComposerSvr" FileKey="ComposerSvr.exe"
ExeCommand="/REGSERVER" Return="ignore" Execute="deferred"
Impersonate="no" />

and scheduled it to run before InstallFinalize.  The result is that 19
times out of 20 it would not run, but once in 20 it would.  I think this
was a race-condition, but I do not know what resources were in
condition, nor why.  Have you seen similar 

Possible solutions, which might work for you (they didn't for me):

Visual Studio .NET has a RegCap.exe which can emit registry keys for EXE
and DLLs, you could use these to transform these into WiX syntax.
RegSvrEx is another such utility.  Both of these are described at
http://www.codeproject.com/w2k/regsvrex.asp?df=100&forumid=14060&exp=0&s
elect=388354.

RegSpy is another such utility, described at
http://www.installsite.org/pages/en/msi/tips.htm (look for the heading
"Capture Self-Registration Information").

If you happen to have Wise Package Studio, it has a setup capture tool
that can monitor the registration of an EXE and capture the changes to
the registry by comparing a snapshot it takes before and after.  It also
intelligently weeds out the changes that are irrelevant (like the most
recently used files data, etc.)

Finally, the one last thing I intend to try (haven't had time yet) is to
take the before and after snapshots of the registry myself, diff them,
and use that as the basis for building the equivalent WiX syntax.

Anyone else on the list have any suggestions, or comments on these?

Raj



________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dan Hoeger
Sent: Friday, September 07, 2007 12:31 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Installing a COM Server EXE



What is the best way to register this Com server

 

Tallow or Heat only seem to work with DLL files that support
DLLRegisterServer

 

Do we make a custom action that launches the EXE with the -regserver and
a corresponding -unregister for the install, uninstall and rollback?

 

What have other people done in the past?

 

Thanks,

 

Dan


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to