Step 2: Checking for Previously Referenced Assemblies
If the requested assembly has also been requested in previous calls, the common language runtime uses the assembly that is already loaded. This can have ramifications when naming assemblies that make up an application. For more information about naming assemblies, see Assembly Names.
If a previous request for the assembly failed, subsequent requests for the assembly are failed immediately without attempting to load the assembly. Starting with the .NET Framework version 2.0, assembly binding failures are cached, and the cached information is used to determine whether to attempt to load the assembly.
.gif) Note |
|---|
To revert to the behavior of the .NET Framework versions 1.0 and 1.1, which did not cache binding failures, include the <disableCachingBindingFailures> Element in your configuration file. |
See Also
Reference
<disableCachingBindingFailures> Element
Concepts
How the Runtime Locates Assemblies
Deployment Scenarios for .NET Framework Applications
Step 1: Examining the Configuration Files
Step 3: Checking the Global Assembly Cache
Step 4: Locating the Assembly through Codebases or Probing
Partial Assembly References