Protecting DLLs

[Jean-Pierre Scerri via DotNetMonster.com]

In my DLLs, I'm protecting my modules as follows

<StrongNameIdentityPermission(SecurityAction.LinkDemand, _
PublicKey:="00240000048000009400000006020000" + _
"00240000525341310004000001000100" + _
"c17577e2aa99d873e07f896b4dc8233d" + _
"687fbfac6e0b0b403b997f75a2b252ff" + _
"ae47abf328bf4481d2184460e3d364b0" + _
"ed7bba85d6ddd96f994e3397ea817ef3" + _
"871ff0cfbd5590ffbba44963ae5e8784" + _
"de51b58df9059d4eda4dd638a4ae147a" + _
"d2f3a5b674780b330cedd93d27a37728" + _
"1c6056092c2ac48a8b27c53631f7d5b6")> _
Public Module xyz
...
End Module

When I try to access that module from another EXE, it is raising an exception (correctly).

Now, my question, how can I make my EXEs access that module??

Thanks in Advance

JP

 

[Mattias Sjögren]

Now, my question, how can I make my EXEs access that module??

Give it a strong name (with the AssemblyKeyFile or AssemblyKeyName
attributes) that matches the public key you have specified.



Mattias

 

[Jean-Pierre Scerri via DotNetMonster.com]

Like

<Assembly: AssemblyKeyFile("V:\Support.dev\Support.snk")>

in the AssemblyInfo.VB ??

 

[Derek Martin]

Yep

 

[Guest]

I'm new to using Public Keys so maybe you could help a bit. How do I create
the "v:\Support.dev\Support.snk" file?

 

[Jean-Pierre Scerri via DotNetMonster.com]

You will have to generate a key usting SN.EXE Command. Search on the help file for some examples.

 

[Guest]

Thanks.