Self registering a COM dll in a VS2003 Windows setup project...

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Rodzilla (rodzilla_at_softwareonsailboats.com)
Date: 12/17/04

  • Next message: balu: "getting message over system tray" 
    Date: Fri, 17 Dec 2004 23:00:37 GMT

    Hi all...If anyone has had experience creating a Windows Setup project that
    includes a customized Redemption dll, we could sure benefit from your
    experience. These questions are very Redemption specific...(
    http://www.dimastr.com/redemption/ )

    We are creating a Windows forms application in Visual Studio/Visual
    Basic/2003 and using an excellent 3rd party COM dll called Redemption to
    access Outlook.
    ...( http://www.dimastr.com/redemption/ )

    We have used Redemption's utility and followed their
    instructions to create a customized version of the Redemption COM dll. The
    problem is getting the customized Redemption COM dll to self register on any
    target machines when installed via a Windows Setup/msi process..

    So far, the only way I can get the customized dll to work on ANY machine is
    to open a command window and use regsvr32.exe to register the customized dll
    on that machine. I have not been able to make a customized Redemption dll
    self register
    when installed through the .msi installation process, and our users will not
    want to or be able to manually register a dll.... We have tried changing the
    dll's Register properties in the Setup project (vsdraCOMRelativePath,
    vsdraCOM) to no avail...

    So my questions are:

    1) After I have created a customized Redemption dll, how should the
    customized dll get properly registered on my development machine? (So far I
    have used regsvr32.exe to manually register the dll on my development
    system. Is this the proper process? Is there another way? So far, if I don't
    register the custom Redemption dll using regsvr32, the program fails.)

    2) When using Visual Studio 2003/Visual Basic and a Windows forms
    application, what steps & settings are necessary in a Windows Setup project
    to insure that the customized Redemption dll will be self registered on the
    target system when my program is installed?

    Thanks in advance for any help you might have...

    Rod Kimmel

  • Next message: balu: "getting message over system tray"

    Relevant Pages

    • Re: Self registering a COM dll in a VS2003 Windows setup project...
      ... projects - a program project and a setup project. ... the customized Redemption dll included as a reference. ... My remaining problem is that when I un-install, the register still has a ...
      (microsoft.public.dotnet.framework.setup)
    • Outlook Redemption & registering a COM dll through Windows setup...
      ... problem is getting the customized Redemption dll to self register on any ... to open a command window and use regsvr32.exe to register the customized dll ... dll's Register properties in the Setup project (vsdraCOMRelativePath, ... what steps & settings are necessary in a Windows Setup project ...
      (microsoft.public.outlook.interop)
    • Re: Self registering a COM dll in a VS2003 Windows setup project...
      ... You might have both a regular COM DLL requiring regsvr32-type ... > the customized Redemption dll included as a reference. ... > option for the Register property - only vsdraCOMRelativePath and vsdraCOM, ...
      (microsoft.public.dotnet.framework.setup)
    • Re: Self registering a COM dll in a VS2003 Windows setup project...
      ... Most of the Register settings extract the settings at build time and put the ... at install time. ... code in that DLL is doing something that isn't being put into the MSI file. ... I have not been able to make a customized Redemption dll ...
      (microsoft.public.dotnet.framework.setup)