Results 1 to 4 of 4

Thread: COM Extraction fails

  1. #1
    Join Date
    Oct 2001
    Posts
    44,727

    COM Extraction fails



    I have a DLL that the extraction tool fails to extract the InProcHandler32
    information. Should this be extracted??

    Scott


  2. #2
    Join Date
    Oct 2001
    Posts
    44,727

    Re: COM Extraction fails



    Maybe I'm misunderstanding what you're asking, but the InprocServer32 data
    is the location of the COM server after it's been installed on the system,
    so it can't extract that path at extraction time. ISWI will build the MSI
    tables so that InprocServer32 gets set up by the installer at install time
    to point to the actual location of the DLL on the client system.

    "Scott Parks" <wsparks@slb.com> wrote in message
    news:3bddc6fe@news.installshield.com...
    > I have a DLL that the extraction tool fails to extract the InProcHandler32
    > information. Should this be extracted??
    >
    > Scott
    >
    >


  3. #3
    Join Date
    Oct 2001
    Posts
    44,727

    re:COM Extraction fails



    I see you said InProcHandler32, but the same principle applies. The biq
    question is whether the InProcHandler32 key shows up in the final msi file
    anywhere, or on the actual client system after the install.

    "Phil Wilson" <phil.wilson@unisys.com> wrote in message
    news:3be99c68@news.installshield.com...
    > Maybe I'm misunderstanding what you're asking, but the InprocServer32 data
    > is the location of the COM server after it's been installed on the system,
    > so it can't extract that path at extraction time. ISWI will build the MSI
    > tables so that InprocServer32 gets set up by the installer at install time
    > to point to the actual location of the DLL on the client system.
    >
    > "Scott Parks" <wsparks@slb.com> wrote in message
    > news:3bddc6fe@news.installshield.com...
    > > I have a DLL that the extraction tool fails to extract the
    InProcHandler32
    > > information. Should this be extracted??
    > >
    > > Scott
    > >
    > >
    >
    >


  4. #4
    Join Date
    Oct 2001
    Posts
    44,727

    re:COM Extraction fails



    No it does not show up on the target system. If on the target system you run
    regsvr32, then it will appear.

    Scott
    "Phil Wilson" <phil.wilson@unisys.com> wrote in message
    news:3be9a3c5@news.installshield.com...
    > I see you said InProcHandler32, but the same principle applies. The biq
    > question is whether the InProcHandler32 key shows up in the final msi file
    > anywhere, or on the actual client system after the install.
    >
    > "Phil Wilson" <phil.wilson@unisys.com> wrote in message
    > news:3be99c68@news.installshield.com...
    > > Maybe I'm misunderstanding what you're asking, but the InprocServer32
    data
    > > is the location of the COM server after it's been installed on the
    system,
    > > so it can't extract that path at extraction time. ISWI will build the
    MSI
    > > tables so that InprocServer32 gets set up by the installer at install
    time
    > > to point to the actual location of the DLL on the client system.
    > >
    > > "Scott Parks" <wsparks@slb.com> wrote in message
    > > news:3bddc6fe@news.installshield.com...
    > > > I have a DLL that the extraction tool fails to extract the
    > InProcHandler32
    > > > information. Should this be extracted??
    > > >
    > > > Scott
    > > >
    > > >
    > >
    > >
    >
    >


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •