Export (0) Print
Expand All

<runtime> Element

Updated: May 2011

Contains information about assembly binding and garbage collection.

<configuration> Element
  <runtime> Element
<runtime>
</runtime>

The following sections describe attributes, child elements, and parent elements.

Attributes

None.

Child Elements

Element

Description

<alwaysFlowImpersonationPolicy>

Specifies that the Windows identity always flows across asynchronous points, regardless of how impersonation was performed.

<assemblyBinding> Element for <runtime>

Contains information about assembly version redirection and the locations of assemblies.

<bypassTrustedAppStrongNames> Element

Specifies whether strong name verification for trusted assemblies should be bypassed.

<developmentMode>

Specifies whether the runtime searches for assemblies in directories specified by the DEVPATH environment variable.

<disableCachingBindingFailures>

Specifies whether the caching of binding failures, which is the default behavior in the .NET Framework version 2.0, is disabled.

<enforceFIPSPolicy>

Specifies whether to enforce a computer configuration requirement that cryptographic algorithms must comply with the Federal Information Processing Standards (FIPS).

<gcConcurrent>

Specifies whether the common language runtime runs garbage collection concurrently.

<gcServer>

Specifies whether the common language runtime runs server garbage collection.

<legacyImpersonationPolicy>

Specifies that the Windows identity does not flow across asynchronous points, regardless of the flow settings for the execution context on the current thread.

<legacyV1CASPolicy>

Specifies whether the runtime uses legacy code access security (CAS) policy.

Parent Elements

Element

Description

configuration

The root element in every configuration file used by the common language runtime and .NET Framework applications.

In the .NET Framework version 2.0, the impersonated identity flows across asynchronous points within an application domain. In the .NET Framework version 2.0, you can enable or disable the flow of impersonation across asynchronous points by properly configuring the runtime element in the machine.config file or in the application configuration file. For ASP.NET, the impersonation flow can be configured in the aspnet.config file found in the <Windows Folder>\Microsoft.NET\Framework\vx.x.xxxx directory.

By default ASP.NET disables the impersonation flow in aspnet.config file by using the following configuration settings:

configuration>
   <runtime>
      <legacyImpersonationPolicy enabled="true"/>
      <alwaysFlowImpersonationPolicy enabled="false"/>
   </runtime>
</configuration>

In ASP.NET, if you want to allow the flow of impersonation instead, you must explicitly use the following configuration settings:

<configuration>
   <runtime>
      <legacyImpersonationPolicy enabled="false"/>
      <alwaysFlowImpersonationPolicy enabled="true"/>
   </runtime>
</configuration>

For more information, see <legacyImpersonationPolicy> Element and <alwaysFlowImpersonationPolicy> Element.

The following example shows how to redirect one assembly version to another.

<configuration>
   <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
         <dependentAssembly>
            <assemblyIdentity name="myAssembly"
                              publicKeyToken="32ab4ba45e0a69a1"
                              culture="neutral" />
             <bindingRedirect oldVersion="1.0.0.0"
                              newVersion="2.0.0.0"/>
         </dependentAssembly>
      </assemblyBinding>
   </runtime>
</configuration>

Date

History

Reason

May 2011

Added missing <enforceFIPSPolicy> element.

Customer feedback.

Community Additions

ADD
Show:
© 2015 Microsoft