We have an application which load all *.dll from app directories. Is there
some way to say which can be loaded and which not? All will be strong named
and can be digitally signed.

Some of our customers can develop asseblies (dll) and when they put dll into
our app directory our app can load it and use cutomer's functions. But not
all custumers can do that.
It is about licencing of our product.
We now start to using strong named asseblies to hold consistency of our
application I think the right name is dll hell.

How can I refuse loading assemblies using security like strong name or
digital sign of assembly.


Thanks Ales
P.S. sorry for my poor english

I did search the forum and I found some usefull help, but when I use
Assembly.LoadFrom and then I try to compare PublicToken of loaded assembly
and the test does not pass, the assebly is currently loaded in my
AppDomain.CurrentDomain. Is there some better solution. Or I have to do that
this way?
If I have do it this way, what is better solution compare PublicToken of
assembly or use PublisherMembershipCondition to check Authenticode.
Thank you

"ales" wrote: