Hi,
My main application is calling a couple of dll assembly that we made. I
want to secure those dll assembly so they can't be used by a third party.
I did a couple of test with
[assembly: AssemblyKeyFile(@"..\..\myKey.snk")] on both side, caller and
dll assembly, but does not succeed to secure the assembly. (myKey.snk is
gnerated with 'sn -k myKey.snk')
and I've read this article
http://www.morganskinner.com/Article...ityPermission/
and in this case we paste the key in the code of the dll assembly like this:
[StrongNameIdentityPermission ( SecurityAction.Demand ,
PublicKey="00240000048000009400000006020000" +
"..." +
"1c6056092c2ac48a8b27c53631f7d5b6")]
But what happen when this key has to change in 50 dlls, can it be taken
from a file?
So I would liks to know what is the best way to secure the dll assembly?
Thanks
Marty