Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>One other thing you may want to check is that, according to this <a href="http://blogs.msdn.com/shawnfa/archive/2005/02/04/367390.aspx" rel="nofollow noreferrer">article</a>, there are some .NET Types that can not be used within a partially trusted assembly, even if it has been decorated with AllowPartiallyTrustedCallersAttribute. </p> <p>See <a href="http://msdn.microsoft.com/en-us/library/aa302328.aspx" rel="nofollow noreferrer">.NET Framework Assemblies and the AllowPartiallyTrustedCallers Attribute</a> for a full list.</p> <p><strong>Update 2</strong> Are you sure all the third-party assemblies you are calling are also decorated with the AllowPartiallyTrustedCallers attribute? </p> <p>eg looking at the AssemblyInfo.cs for PagedList 1.1 it does not seem to contain this attribute. </p> <p><strong>Update 1</strong>: You are right, that list of unusable types does look very dated.</p> <p>This <a href="http://msdn.microsoft.com/en-us/library/bb386929.aspx" rel="nofollow noreferrer">LINQ to SQL</a> FAQ has some interesting information regarding its usage in a partial trust environment: </p> <blockquote> <p>APTCA</p> <p>Q. Is System.Data.Linq marked for use by partially trusted code?</p> <p>A. Yes, the System.Data.Linq.dll assembly is among those .NET Framework assemblies marked with the AllowPartiallyTrustedCallersAttribute attribute. Without this marking, assemblies in the .NET Framework are intended for use only by fully trusted code.</p> <p>The principal scenario in LINQ to SQL for allowing partially trusted callers is to enable the LINQ to SQL assembly to be accessed from Web applications, where the trust configuration is Medium.</p> </blockquote>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload