Re: strong name exception on SecurityAction.Demand, works fine for LinkDemand

Hi, 

you know that SNIP really only has teeth when the client is partially trusted?

- in fact the behaviour has changed in 2.0 that fully trusted code always passes SNIP demands.

i wouldn't invest in this feature.

but this doesn't answer your question - 

a demand triggers a full stack walk

i guess you signed your code behind assembly?

so the page class (not signed) derives from the code behind class (signed) to call into a SNIP demand - the stack walk fails when the page class is reached.

---------------------------------------
Dominick Baier - DevelopMentor
http://www.leastprivilege.com

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 ***



.

Relevant Pages

  • Re: Ride-A-Lot should post...
    ... Sorry, I dont believe it. ... computers. ... Calling sombody on the phone to ...
    (alt.mountain-bike)
  • Re: Ride-A-Lot should post...
    ... Sorry, I dont believe it. ... computers. ... Calling sombody on the phone to ...
    (alt.mountain-bike)
  • Re: Is David Fenton right about error handling?
    ... > to be opened has a number of checks in its on open event. ... > the continuous for or sub form datasheet on the calling form. ... What I did for this was create a wrapper function for ...
    (comp.databases.ms-access)
  • Re: The Stupid Squad strikes again
    ... <huge snip> ... obviously it upsets him. ... you calling yourself a term that was originally an insult is ... originally an insult differs how, ...
    (alt.smokers.cigars)
  • Re: Can this be more efficient?
    ... it's not a good idea to use & when calling a subroutine. ... This was necessary for Perl4 and before, but that is at least 10 years ...
    (comp.lang.perl.misc)