Registering COM in VS.NET C# Standard Version Setup Project

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Takuya Matsumoto

    Registering COM in VS.NET C# Standard Version Setup Project

    Greetings to all,

    I am creating a setup project for a COM component I created in C#, but I
    can't get the component to be registered in the client system.
    What I would like to achieve is an equivalent of manually registering it
    with "gacutil.ex e" and then with "regasm.exe ".

    I went though the support documents and read the below, but the options I
    have are differenct:


    Could it be because I only have C# 2003 Standard Version?
    The project I am using is a "Setup Project", not "Deployment Project"as the
    latter is not available on the Standard Version.
    The options I have under "register" are "vsdraCOM" and
    "vsdraCOMRelati vePath" of which I have tried both.

    Any thoughts?

    Thanks!

    Takuya

  • Takuya Matsumoto

    #2
    Re: Registering COM in VS.NET C# Standard Version Setup Project

    Further to my previous post, I've been trying to figure it out and something
    strange is happening with regasm.exe.

    What I did was create a registry file by using:
    regasm control.dll /reg:control.reg
    then import the reg file to the Setup Project.

    I then installed the control by running the installer, but this doesn't seem
    to do the job.
    So,I manually registered it using regasm whithout uninstalling the
    installer, then the control works happily.

    It seems like the regasm does more work when it registers a file than what
    it creates in the reg file.

    Is it possible?

    Takuya



    "Takuya Matsumoto" <adminCAPS_FOR_ SPAM_AND_VIRUS_ PROTECTION@saka ecorp.co.jp>
    wrote in message news:uI%23BhdJn DHA.2000@TK2MSF TNGP12.phx.gbl. ..[color=blue]
    > Greetings to all,
    >
    > I am creating a setup project for a COM component I created in C#, but I
    > can't get the component to be registered in the client system.
    > What I would like to achieve is an equivalent of manually registering it
    > with "gacutil.ex e" and then with "regasm.exe ".
    >
    > I went though the support documents and read the below, but the options I
    > have are differenct:
    >[/color]
    http://msdn.microsoft.com/library/de...erProperty.asp[color=blue]
    >
    > Could it be because I only have C# 2003 Standard Version?
    > The project I am using is a "Setup Project", not "Deployment Project"as[/color]
    the[color=blue]
    > latter is not available on the Standard Version.
    > The options I have under "register" are "vsdraCOM" and
    > "vsdraCOMRelati vePath" of which I have tried both.
    >
    > Any thoughts?
    >
    > Thanks!
    >
    > Takuya
    >[/color]

    Comment

    • Takuya Matsumoto

      #3
      Re: Registering COM in VS.NET C# Standard Version Setup Project

      Again further to my previous post, I did more tests/experiments.

      I checked the registry after installing with the installer, and the some of
      the entries are there.
      It seems like the entries created when I used the "regasm control.dll
      /regfile:control .reg" are registered with the vsdraCOM option in the
      "register" item of the Setup Project, but the actual application still does
      not run.
      When I do "regasm control.dll" manually, it then works perfectly (and the
      gacutil).

      I'm lost as to where this difference in the registration comes from.
      Also, I would really like to find out how the control.dll can be registered
      into Global Assembly Cache automatically using the installer.

      Your help is very much appreciated.

      Cheers,

      Takuya




      "Takuya Matsumoto" <adminCAPS_FOR_ SPAM_AND_VIRUS_ PROTECTION@saka ecorp.co.jp>
      wrote in message news:ubH791RnDH A.1096@TK2MSFTN GP11.phx.gbl...[color=blue]
      > Further to my previous post, I've been trying to figure it out and[/color]
      something[color=blue]
      > strange is happening with regasm.exe.
      >
      > What I did was create a registry file by using:
      > regasm control.dll /reg:control.reg
      > then import the reg file to the Setup Project.
      >
      > I then installed the control by running the installer, but this doesn't[/color]
      seem[color=blue]
      > to do the job.
      > So,I manually registered it using regasm whithout uninstalling the
      > installer, then the control works happily.
      >
      > It seems like the regasm does more work when it registers a file than what
      > it creates in the reg file.
      >
      > Is it possible?
      >
      > Takuya
      >
      >
      >
      > "Takuya Matsumoto"[/color]
      <adminCAPS_FOR_ SPAM_AND_VIRUS_ PROTECTION@saka ecorp.co.jp>[color=blue]
      > wrote in message news:uI%23BhdJn DHA.2000@TK2MSF TNGP12.phx.gbl. ..[color=green]
      > > Greetings to all,
      > >
      > > I am creating a setup project for a COM component I created in C#, but I
      > > can't get the component to be registered in the client system.
      > > What I would like to achieve is an equivalent of manually registering it
      > > with "gacutil.ex e" and then with "regasm.exe ".
      > >
      > > I went though the support documents and read the below, but the options[/color][/color]
      I[color=blue][color=green]
      > > have are differenct:
      > >[/color]
      >[/color]
      http://msdn.microsoft.com/library/de...erProperty.asp[color=blue][color=green]
      > >
      > > Could it be because I only have C# 2003 Standard Version?
      > > The project I am using is a "Setup Project", not "Deployment Project"as[/color]
      > the[color=green]
      > > latter is not available on the Standard Version.
      > > The options I have under "register" are "vsdraCOM" and
      > > "vsdraCOMRelati vePath" of which I have tried both.
      > >
      > > Any thoughts?
      > >
      > > Thanks!
      > >
      > > Takuya
      > >[/color]
      >[/color]

      Comment

      Working...