Re: Manually generating Interop assembly failing......

From: Ollie (why)
Date: 05/26/04

  • Next message: ari: "strong name woes" 
    Date: Wed, 26 May 2004 14:35:39 +0100

    Nick,

    It fails with the same message if I don't delay signing it either....

    The reason I am trying to do this is because I want to save changes into the
    COM Admin Catalog from a COM+ application, and to register a COM+
    application the assembly has to be signed (as you probably know :)) and
    hence all references have to be signed as well.....

    Cheers

    Ollie
    "Nicholas Paldino [.NET/C# MVP]" <mvp@spam.guard.caspershouse.com> wrote in
    message news:eZIjaQyQEHA.1960@TK2MSFTNGP10.phx.gbl...
    > Ollie,
    >
    > Is there a need to delay sign the interop assembly? Can you just sign
    > it outright?
    >
    >
    > --
    > - Nicholas Paldino [.NET/C# MVP]
    > - mvp@spam.guard.caspershouse.com
    >
    > "Ollie" <ollie_riches@hotmail.com> wrote in message
    > news:uZIxffwQEHA.3140@tk2msftngp13.phx.gbl...
    > > I am trying to generate a strong name assembly from the unmanaged DLL
    for
    > > the COM + 1.0 Admin Type Library located in the
    > > C:\WINDOWS\system32\Com\comadmin.dll, but when I run the following
    command
    > > it fails....
    > >
    > > C:\work\BillAnalyser\Bin>tlbimp.exe comadmin.dll /delaysign
    > > /publickey:C:\work\key\billanalyser.snk /out:Fb.Interop.ComAdmin.dll
    > >
    > >
    > > It fails saying 'TlbImp error:
    > System.Runtime.InteropServices.COMException -
    > > StrongName APIs could not locate a matching CSP.'
    > >
    > > Anyone got any ideas why as this is driving me crazy....
    > >
    > > Cheers in advance
    > >
    > > Ollie
    > >
    > >
    >
    >

  • Next message: ari: "strong name woes"

    Relevant Pages
    Loading