and how it needs .snk to do it's job.
it needs that the assembly has been strong-named with an SNK (żor
cert?) - however, it doesn't need the actual SNK that was used. The
SNK hash forms part of the full-name of the assembly.
Deploying this may actually present a security risk, in that it would
make it easy for somebody to simulate your dll (including your private
SNK). But generally if somebody can do this they have already
compromised your farm, and you have bigger issues ;-p
Quote:
But if you've been there and done that and can tell my why it's not worthit...
In my view, it is just dll-hell all over again; GAC-hell. Disks are
cheap, and having separate copies provides an additional level of
isolation between apps (i.e. you can upgrade each version individually
without having to stress over version-forwarding policies, etc). It
may suit some scenarios (and is a bitter necessity for some that I
already mentioned), but I generally avoid the GAC.
I'd welcome other views from the floor...
Marc
