Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
60
WebCalendar error Attempt by security transparent method
posted

Hi, I am received the error “Attempt by security transparent method ..” in the form, which includes  WebCalendar  control.  This happened after inserting setting  <trust level="Full" legacyCasModel="true" /> in Web.config. I need it for MS ReportViewer.

Could you help to fix it. Best regards.

Error’s full text: Attempt by security transparent method 'Infragistics.WebUI.Shared.Util.ScriptManager.Init(System.Web.UI.Page)' to access security critical method 'System.Web.UI.ScriptManager.GetCurrent(System.Web.UI.Page)' failed. Assembly 'Infragistics45.WebUI.Shared.v16.1, Version=16.1.20161.2163, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' is marked with the AllowPartiallyTrustedCallersAttribute, and uses the level 2 security transparency model. Level 2 transparency causes all methods in AllowPartiallyTrustedCallers assemblies to become security transparent by default, which may be the cause of this exception. Assembly 'System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' is a conditionally APTCA assembly which is not enabled in the current AppDomain. To enable this assembly to be used by partial trust or security transparent code, please add assembly name 'System.Web.Extensions, PublicKey=0024000004800000940000000602000000240000525341310004000001000100B5FC90E7027F67871E773A8FDE8938C81DD402BA65B9201D60593E96C492651E889CC13F1415EBB53FAC1131AE0BD333C5EE6021672D9718EA31A8AEBD0DA0072F25D87DBA6FC90FFD598ED4DA35E44C398C454307E8E33B8426143DAEC9F596836F97C8F74750E5975C64E2189F45DEF46B2A2B1247ADC3652BF5C308055DA9' to the the PartialTrustVisibleAssemblies list when creating the AppDomain

  • 21795
    Offline posted

    Hello Maratas,

    Our developers have investigated this issue and it appears to be by design. Since version 2012 volume 2 Infragistics assemblies are signed with partial trust permissions. Changing this level could affect other applications that are using Infragistics assemblies and expect them to be with partial trust permissions.

    As a workaround which maintains the legacyCasModel="true" you can set the trust level to:

    <trust level="High" legacyCasModel="true"/>

    Both High and Medium levels work.

    Please let me know if you need any further questions on this matter.

  • 21795
    Offline posted

    Hello Maratas,

    I have investigated your issue and was able to reproduce the behavior you have described. I have asked our engineering staff to examine this further. To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of #247805. This will be assigned to a developer in a future sprint to review my investigation and confirm my findings or to offer a fix, or other resolution.

    Thank you for using Infragistics components.