Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

<disableCachingBindingFailures> Element

Specifies whether to disable the caching of binding failures that occur because the assembly was not found by probing.

<configuration> Element
  <runtime> Element
    <disableCachingBindingFailures> Element
<disableCachingBindingFailures enabled="0|1"/>

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

Attributes

Attribute

Description

enabled

Required attribute.

Specifies whether to disable the caching of binding failures that occur because the assembly was not found by probing.

enabled Attribute

Value

Description

0

Do not disable the caching of binding failures that occur because the assembly was not found by probing. This is the default binding behavior starting with the .NET Framework version 2.0.

1

Disable the caching of binding failures that occur because the assembly was not found by probing. This setting reverts to the binding behavior of the .NET Framework version 1.1.

Child Elements

None.

Parent Elements

Element

Description

configuration

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

runtime

Contains information about assembly binding and garbage collection.

Starting with the .NET Framework version 2.0, the default behavior for loading assemblies is to cache all binding and loading failures. That is, if an attempt to load an assembly fails, subsequent requests to load the same assembly fail immediately, without any attempt to locate the assembly. This element disables that default behavior for binding failures that occur because the assembly could not be found in the probing path. These failures throw FileNotFoundException.

Some binding and loading failures are not affected by this element, and are always cached. These failures occur because the assembly was found but could not be loaded. They throw BadImageFormatException or FileLoadException. The following list includes some examples of such failures.

  • If you attempt to load a file is not a valid assembly, subsequent attempts to load the assembly will fail even if the bad file is replaced with the correct assembly.

  • If you attempt to load an assembly that is locked by the file system, subsequent attempts to load the assembly will fail even after the assembly is released by the file system.

  • If one or more versions of the assembly that you are attempting to load is in the probing path, but the specific version you are requesting is not among them, subsequent attempts to load that version will fail even if the correct version is moved into the probing path.

The following code example shows how to disable the caching of assembly binding failures that occur because the assembly was not found by probing.

<configuration>
   <runtime>
      <disableCachingBindingFailures enabled="1" />
   </runtime>
</configuration>
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.