Contains information about assembly binding and garbage collection.
The following sections describe attributes, child elements, and parent elements.
Specifies that the Windows identity always flows across asynchronous points, regardless of how impersonation was performed.
Specifies the assembly that provides the application domain manager for the default application domain in the process.
Specifies the type that serves as the application domain manager for the default application domain.
Instructs the runtime to collect statistics on all application domains in the process for the life of the process.
Contains information about assembly version redirection and the locations of assemblies.
Specifies whether strong name verification for trusted assemblies should be bypassed.
Specifies that the runtime should use legacy sorting behavior when performing string comparisons.
Specifies whether the runtime searches for assemblies in directories specified by the DEVPATH environment variable.
Specifies whether the caching of binding failures, which is the default behavior in the .NET Framework version 2.0, is disabled.
Specifies whether the full thread stack is committed when a thread is started.
Specifies whether the default behavior, which is to allow the runtime host to override configuration settings for an application domain, is disabled.
Specifies whether to enforce a computer configuration requirement that cryptographic algorithms must comply with the Federal Information Processing Standards (FIPS).
Specifies whether to enable event tracing for Windows (ETW) for common language runtime events.
Specifies whether PerfCounter.dll uses the CategoryOptions registry setting in a .NET Framework version 1.1 application to determine whether to load performance counter data from category-specific shared memory or global memory.
On 64-bit platforms, enables arrays that are greater than 2 gigabytes (GB) in total size.
Specifies whether the common language runtime runs garbage collection concurrently.
Specifies whether garbage collection supports multiple CPU groups.
Specifies whether the common language runtime runs server garbage collection.
Specifies whether the runtime uses code access security (CAS) publisher policy.
Specifies whether the runtime allows managed code to catch access violations and other corrupted state exceptions.
Specifies that the Windows identity does not flow across asynchronous points, regardless of the flow settings for the execution context on the current thread.
Specifies whether assemblies from remote sources are loaded as full trust.
Specifies whether the runtime uses legacy code access security (CAS) policy.
Specifies whether the runtime automatically fixes incorrect platform invoke declarations at run time, at the cost of slower transitions between managed and unmanaged code.
Specifies whether the runtime uses a fixed amount of memory to calculate hash codes for the StringComparer.GetHashCode method.
Specifies that the runtime will use COM interop instead of remoting across application domain boundaries.
Optimizes the probe for satellite assemblies.
Specifies whether shadow copying uses the default startup behavior introduced in the .NET Framework 4, or reverts to the startup behavior of earlier versions of the .NET Framework.
Specifies that an application can reference the same assembly in two different implementations of the .NET Framework, by disabling the default behavior that treats the assemblies as equivalent for application portability purposes.
Provides configuration information for the default in-memory object cache.
Specifies whether the runtime distributes managed threads across all CPU groups.
Specifies whether unhandled task exceptions should terminate a running process.
Specifies whether the runtime uses legacy formatting for TimeSpan values.
Specifies whether the runtime calculates hash codes for strings on a per application domain basis.
Requests that the runtime use explicit stack sizes when it creates certain threads that it uses internally, instead of the default stack size.
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 the 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>
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="188.8.131.52" newVersion="184.108.40.206"/> </dependentAssembly> </assemblyBinding> </runtime> </configuration>