Re: Error from CAS Config util
From: Nicole Calinoiu (calinoiu)
Date: Thu, 10 Mar 2005 06:56:38 -0500
It's a misleading error message. The real problem is that the assembly
needs to be added to the trusted list at each of the enterprise, machine,
and user policy levels, and the UI only lets you target one of these at a
time. To work around this limitation, you'll need to use caspol -af
"Trevor Lawrence" <firstname.lastname@example.org> wrote in message
>I am attempting to construct a custom implementation of
>IMembershipCondition (which actually does a bit of work and then delegates
>to a UrlMembershipCondition object).
> I hjave given it a trong name and successfully installed it in the GAC,
> but an attempt to add it to the policy assemblies in the config msc tool
> gives an error that it couldn't add the assembly as it requires a strong
> name. All checks indicate that it does have a proper strong name. Is the
> tool misleading? Is this a generic message with one suggested cause? The
> actual message was:
> "Unable to add the selected assembly. The assembly must have a strong
> name (name, version and public key)."
> Any hints?
> Trevor Lawrence