[wix-users] Registering an out-of-process COM server

[Adnan Shaheen]

out-of-proc COM registration only can also be done as

<File Id="COMComp" Source="CompPath" Name="CompExe" KeyPath="yes"
Checksum="yes">
                                <TypeLib Id="ComTypeLibGUID" Language="0"
Description="Com Component Type Library" MajorVersion="1" MinorVersion="0">
                                    <AppId Id="CompAppGUID"
LocalService="ComService" Description="ComComp">
                                        <Class Id="ComCompClassGUID"
Description="ComComp Class"
                                               Context="InprocServer32"
ThreadingModel="both">
                                            <ProgId Id="ComComp.Comp.1"
Description="ComComp Class">
                                                <ProgId Id="ComComp.Comp"
Description="ComComp Class"></ProgId>
                                            </ProgId>
                                        </Class>
                                    </AppId>
                                    <Class Id="EnumeratorClassGUID"
Description="ComEnumerator Class" Context="InprocServer32"
ThreadingModel="both" Version="1.0"></Class>
                                </TypeLib>
                            </File>

Provide the GUIDS from your out-of-proc COM component. This will not create
the service for your COM component, if you need one. You'd have to create
the service for your COM component via ServiceInstall WiX element.
Another way of registering the COM component, which could be very stupid is
to find the registry keys, that your COM component creates via some
application, then create those registry key via RegistryKey WiX element,
which is too much of noise and may not work on all os you support.

Regards:
Adnan Shaheen.


On Sat, 16 Mar 2019 at 11:20, Rob Mensching via wix-users <
wix-users at lists.wixtoolset.org> wrote:

> Heat does not have the ability to capture out-of-proc COM registration.
> It's quite a challenging thing to do.
>
> We built a commercial harvesting solution that supports out-of-proc COM (
> https://www.firegiant.com/wix/wep-documentation/harvesting/selfreg/).
> It's available via the FireGiant WiX Expansion Pack (
> https://www.firegiant.com/products/wix-expansion-pack/).
>
> _____________________________________________________________
>  Short replies here. Complete answers over there:
> http://www.firegiant.com/
>
> -----Original Message-----
> From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of
> Sean Farrow via wix-users
> Sent: Saturday, March 16, 2019 2:26 AM
> To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
> Cc: Sean Farrow <sean.farrow at seanfarrow.co.uk>
> Subject: [wix-users] Registering an out-of-process COM server
>
> Hi,
>
> Does WiX/Heat have a way of capturing the entries required to register an
> out-of-process COM server in an executable.
>
> Or, is there another way of doing this? I'm looking to be able to add
> registry entries to the component that houses the server executable file.
>
> Any help appreciated.
> Kind regards
> Sean.
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>