Assigning Strong Name to COM dlls -- dotnet security

dotnet security : Assigning Strong Name to COM dlls

Dominick Baier
7/31/2006 3:16:12 PM

Hi,

you have to sign the runtime callable wrapper - tlbimp has a /keyfile option.

dominick

[quoted text, click to view]

Dominick Baier
7/31/2006 3:51:49 PM

Hi,

when you add a reference to a COM DLL in VS - they call tlbimp.exe under
the cover (which can be found in the framework directory).

You have to do that manually, and reference the interop assembly directly.

I have a look at the correct command lines switches if you don't get that
to work (but thats fairly straightforward).

dominick

[quoted text, click to view]

Usman Jamil
7/31/2006 8:06:47 PM

Hi

I've a dotnet project that has refrences of some COM components written in
VC++. I have not been able to assign my dotnet project a strong name because
this COM refrence is strongly named. Can someone please tell me that how can
I assign strong name to this com component too. Somewhere in the group I
read that tlbimp.exe is used to strongly name the interop dll of that COM.
Please help me with the exact command parameters to set to do so.

Regards

Usman

Usman Jamil
7/31/2006 8:38:32 PM

I guess runtime callable wrapper is the interop created by adding the
refrence of that com. Can you please tell me that exact command to use if I
have following files. and I've to assign strong name to dotnetApp.exe and
the runtime callable wrapper.

1. dotnetApp.exe
2. TestCom.dll
3. Interop.TestComlib.dll
4. TestKey.snk (file generated using SN.exe as SN.exe -k TestKey.snk)

Regards

Usman

"Dominick Baier" <dbaier@pleasepleasenospam_leastprivilege.com> wrote in
message news:4580be63a2028c882dc2840db4f@news.microsoft.com...
[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet security

home · blog · groups

Questions? Comments? Contact the dn