By default a strongly-named assembly can only be called by full-trusted callers. I think this is intended as a 'secure by default' setting, because it should reduce the chances of someone being able to use the luring attack on such an assembly.
But if you want your strongly-named assembly to be callable by partially trusted callers, just apply the AllowPartiallyTrustedCallersAttribute to your assembly: [assembly:AllowPartiallyTrustedCallersAttribute] Although this class itself still appears to be undocumented in the latest MSDN, it is mentioned in the "Version 1 Security Changes for the Microsoft .NET Framework" page, which on my installation is here: ms-help://MS.VSCC/MS.MSDNQTR.2002APR.1033/dnnetsec/html/v1securitychanges.ht m That URL will probably only work if you have the April 2002 MSDN installed by the looks of it... So the idea is that unless you have explicitly declared that you think your component will be robust in the face of malicious code calling into it, such code will not even be given the chance to try. -- Ian Griffiths DevelopMentor ----- Original Message ----- From: "Wayne Kelly" <[EMAIL PROTECTED]> > It appears that to refer to a strongly named assembly, you need to > be executing with the "Full Trust" permission set". You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
