strong name exception on SecurityAction.Demand, works fine for LinkDemand
- From: Joe Abou Jaoude <anonymous@xxxxxxxxxx>
- Date: Thu, 29 Dec 2005 05:27:16 -0800
Hi,
I have a component that is protected by the
StrongNameIdentityPermission.
I m calling this component from a web application that has the
appropriate strong name.
I noticed that calling the component fails when the
SecurityAction.Demand is on, while it succeeds when
SecurityAction.LinkDemand is on.
Since I m calling the component directly from my application, I was
wondering , what could be in the method stack that is causing the demand
to fail.
Is there a way to make it work ?
Regards
*** Sent via Developersdex http://www.developersdex.com ***
.
- Follow-Ups:
- Re: strong name exception on SecurityAction.Demand, works fine for LinkDemand
- From: Dominick Baier [DevelopMentor]
- Re: strong name exception on SecurityAction.Demand, works fine for LinkDemand
- Prev by Date: Re: ASP.NET IMPERSONATION AND ORACLE 8.1.7
- Next by Date: Re: LDAP and SASL
- Previous by thread: Re: ASP.NET 2.0 Profile/Membership/Forms Authentication - Manual Login
- Next by thread: Re: strong name exception on SecurityAction.Demand, works fine for LinkDemand
- Index(es):
Relevant Pages
|
|