Re: Can't create strong named assemblies if any referenced assembly references COM

From: Ivan Medvedev [MS] (ivanmed_at_online.microsoft.com)
Date: 09/25/03 

Date: Thu, 25 Sep 2003 10:24:38 -0700

Daryl -
you are probably creating non strongname signed assemblies wrapping your COM
components. If you are using tlbimp.exe to create them you can use /keyfile
option to get them signed.
--Ivan
http://blogs.gotdotnet.com/ivanmed
This message is provided "AS IS" with no warranties, and confers no rights.

"Daryl Salisbury" <darylswork@hotmail.com> wrote in message
news:f41b01c382f2$edc011b0$a601280a@phx.gbl...
> Hi I'm having some issues created strong named assemblies
> in .NET 2003...
>
> After setting the AssemblyKeyFile attribute in the
> assembly info for all projects most of them compile OK..
>
> however there is one project which references a COM DLL in
> order to interface with a third party application... I'm
> getting an error that says the Interop assembly doesn't
> have a strong name...
>
> Normally I would use a createobject call to use this COM
> dll in this case however the DLL raises events..
>
> Any idea what I can do to resolve this and use strong
> names?

Relevant Pages

  • Re: Cant create strong named assemblies if any referenced assembly references COM
    ... you are probably creating non strongname signed assemblies wrapping your COM ... > dll in this case however the DLL raises events.. ...
    (microsoft.public.dotnet.security)
  • Re: .NET dll config file
    ... > application has some other .NET dll references. ... assemblies to a separate folder you create problems because you have to tell ... So if your library is called by a "third party application" ... You cannot create a config file just for your DLL. ...
    (microsoft.public.dotnet.framework)
  • Re: WinSxS, functional under 2k ?
    ... The newSide-by-Side Assembly technology was introduced with Windows XP to help reduce or eliminate DLL Hell. ... If you recall earlier Windows versions, like Windows 95, when you installed an application you were warned if the installer tried to replace a DLL from the system folder with an older version and you were asked if you wanted to accept the change. ... Until Windows XP it wasn't so easy to use different versions of shared system DLLs, that is what the new Side-by-Side assemblies attempts to resolve. ...
    (microsoft.public.win2000.general)
  • Re: Trusted Assemblies are untrusted after being overwritten
    ... ongoing application where features are added now ... IIS servers that need to run this application, ... directory structure, of course, contains the .DLL ... >between the two assemblies. ...
    (microsoft.public.inetserver.iis.security)
  • Re: regsvr32 error code 0x80004002
    ... VC assembly failed to load. ... but there are no relevant events in the Event Viewer. ... If a DLL was built with Visual Studio 2005 SP1 and was compiled to use the ... Private assemblies must be used. ...
    (microsoft.public.vc.mfc)