Runtime Settings Schema
Runtime settings specify how the common language runtime handles garbage collection and the version of an assembly to use in configuration files.
<alwaysFlowImpersonationPolicy>
<assemblyBinding> Element for <runtime>
<disableCachingBindingFailures>
Element |
Description |
---|---|
Specifies that the Windows identity always flows across asynchronous points, regardless of how impersonation was performed. |
|
Contains information about assembly version redirection and the locations of assemblies. |
|
Contains identifying information about an assembly. |
|
Redirects one assembly version to another. |
|
Specifies where the runtime can find an assembly. |
|
Encapsulates binding policy and assembly location for each assembly. |
|
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 starts. |
|
Specifies whether to enforce a computer configuration requirement that cryptographic algorithms must comply with the Federal Information Processing Standards (FIPS). |
|
Specifies whether the runtime runs garbage collection concurrently. |
|
Specifies whether the common language runtime runs server garbage collection. |
|
Specifies that the Windows identity does not flow across user-defined asynchronous points. |
|
Specifies whether the runtime uses legacy code access security (CAS) policy. |
|
Specifies subdirectories that the runtime searches when loading assemblies. |
|
Specifies whether the runtime applies publisher policy. |
|
Specifies the full name of the assembly that should be dynamically loaded when a partial name is used. |
|
Contains information about assembly binding and the behavior of garbage collection. |
See Also
Tasks
How to: Disable Concurrent Garbage Collection
Concepts
Other Resources
Configuration File Schema for the .NET Framework
Change History
Date |
History |
Reason |
---|---|---|
May 2011 |
Added missing <enforceFIPSPolicy> element. |
Customer feedback. |