Re: Interop Forms Toolkit - how to determine if worked

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

    Re: Interop Forms Toolkit - how to determine if worked

    This time I agree with Bill replying to a .Net related Q, even if it hurts
    :))
    No need to kick on Bill everytime he is posting in this group. Fair is fair.

    /Henning

    "Kevin Provance" <kevin@remove_t pasoft_remove.c omskrev i meddelandet
    news:%23qLKOL4S JHA.5568@TK2MSF TNGP05.phx.gbl. ..
    Please post all follow ups here so they go to the correct group, which is
    not here.
    >
    "Bill McCarthy" <Bill@localhost .comwrote in message
    news:%234r0sV3S JHA.1960@TK2MSF TNGP04.phx.gbl. ..
    | Hi Kevin,
    |
    | <Kevin.M.Jonas@ gmail.comwrote in message
    |
    news:5731aa12-2185-45df-aee0-331f18c3b5c3@x1 4g2000yqk.googl egroups.com...
    | >I am using the Visual Basic Interop Forms Toolkit to help with
    | migrating form VB to .NET. I think my problem is related to this. I
    | have a client that when the form witht he Interop control is displayed
    | it fails with a Run-time 372 error.
    | >
    | How do I determine if the files are registered correctly. The
    | assembly is registered with mscorlib, correct? On a side note if I
    | run regasm as an Administrator I get access denied. This might be
    | related then.
    | >
    |
    |
    | So to be clear, you are running a VB6 application which is giving you
    error
    | 327, which usually means COM component not found, correct ?
    |
    | For VB6 the COM components either need to be registered or you use
    regfree
    | COM with SxS. I haven't tried regfree with a COM wrapped .NET control
    but
    | it should work the same as any COM control. I know you can definitely
    use
    | COM controls from .NET using regfree SxS. So that's one avenue you
    could
    | look at.
    | If you are registering the control, then yes you use regasm. If you
    can't
    | access that, I think that's where your problem is. Regasm isn't by
    default
    | in the path, so you will need to specify it such as
    | %windir%\Micros oft.NET\Framewo rk\v2.0.50727\r egasm.exe.
    | As to testing to see if it is entered correctly in the registry, you can
    run
    | regasm with the /regfile switch and that will output the relevant
    registry
    | entries into a file for you. You can then compare those entries to what
    is
    | on the computer.
    | The other thing to look at is where you put your assembly. It either
    has
    to
    | be in the application directory or in the global assembly cache.
    |
    |
    >
    >

Working...