System.MethodAccessException: Attempt by security transparent method to access security critical method fails on all applications

Question

Hello and thanks in advance for the help, I know that this question or similar questions have been posted, frequently with specific regards to MVC 3 applications. However, I am getting this error message whenever I try and launch any application from within visual web developer express 2010 using a .net 4.0 target framework.

The exact error message is:

Attempt by security transparent method 'System.Runtime.Diagnostics.DiagnosticTrace..ctor(System.String, System.Guid)' to access security critical method 'System.Runtime.Diagnostics.EtwDiagnosticTrace..ctor(System.String, System.Guid)' failed`.

Assembly 'System.ServiceModel.Internals, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' 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.

Stack trace:

[MethodAccessException: Attempt by security transparent method 'System.Runtime.Diagnostics.DiagnosticTrace..ctor(System.String, System.Guid)' to access security critical method 'System.Runtime.Diagnostics.EtwDiagnosticTrace..ctor(System.String, System.Guid)' failed.

Assembly 'System.ServiceModel.Internals, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' 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.]
   System.Runtime.Diagnostics.DiagnosticTrace..ctor(String traceSourceName, Guid etwProviderId) +24
   System.ServiceModel.Activation.FxTrace.InitializeTracing() +90
   System.ServiceModel.Activation.FxTrace.get_Trace() +84
   System.ServiceModel.ServiceHostingEnvironment.EnsureInitialized() +59
   System.ServiceModel.ServiceHostingEnvironment.OnEnsureInitialized(Object state) +4
   System.ServiceModel.AspNetPartialTrustHelpers.PartialTrustInvoke(ContextCallback callback, Object state) +52
   System.ServiceModel.ServiceHostingEnvironment.SafeEnsureInitialized() +65
   System.ServiceModel.Activation.HttpModule.ProcessRequest(Object sender, EventArgs e) +58
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +143
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +69

I am completely at a loss here. If I create just any basic application from scratch and try and launch it, even with nothing added, I get this error screen. I have tried removing the target framework="4.0" attribute from the

<compilation debug="true" targetFramework="4.0" />

tag and running it with no results. I have tried removing that attribute and adding

<startup useLegacyV2RuntimeActivationPolicy="true">
  <supportedRuntime version="v2.0.50727"/>
  <supportedRuntime version="v4.0.30319"/>
 </startup>

as suggested in this thread: BadImageFormatException - Is it possible to specify which .NET version is used to run an executable? I tried repairing the .Net 4.0 framework installation because I heard that may be an issue. I just installed visual web developer last night in order to work on a project that I moved over from Microsoft Visual Studio 2010 because my trial version expired, any help or potential workarounds would be appreciated.

Answer 1

I experienced this issue today. As far as I understand it, the problem is that .NET 4.0 assemblies now default to security critical. It's not possible for security transparent code to call into security critical code.

The solution in my case was related to having AllowPartiallyTrustedCallersAttribute defined on only a few of the assemblies in my application. I had to either remove this attribute from all assemblies, or add it to all of them.

Answer 2

You may need to add the following to your AssemblyInfo.cs file so that the involved assemblies are the same.

[assembly: SecurityTransparent()]

Answer 3

Appreciate I'm extremely late to the party here but in VS2013 and suffering the same issue with a .NET 4.5.1 ClickOnce project, I fixed this issue by:

1. Opening the Project Properties of the ClickOnce project in question
2. Opening the Security tab
3. Changing the trust settings to "This is a partial trust application"
4. Changing the trust settings back to "This is a full trust application"

Hope this helps someone else!