.NET determines the required version of dependent assemblies by checking the application's manifest and configuration files, searching the Global Assembly Cache if the assembly is strongly named, and then searching the directory of the executable if not found elsewhere. If the assembly is not located, the application terminates in error.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
33 views1 page
Program Execution - Part 5
.NET determines the required version of dependent assemblies by checking the application's manifest and configuration files, searching the Global Assembly Cache if the assembly is strongly named, and then searching the directory of the executable if not found elsewhere. If the assembly is not located, the application terminates in error.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1
How .
NET finds the assemblies during
program execution- Part 5 1. .NET figures out what version is needed : Usually the information about the dependant assemblies is present in the application's assembly manifest. CLR checks the application configuration file, publisher policy file(if exists), and machine config file for information that overrides the version information stored in the calling assembly's manifest. 2. .NET searches GAC (Global Assembly Cache) : .NET searches GAC only if the assembly is strongly named. 3. If the assembly is not found in the GAC, and if there is a .config file, then .NET searches the location in the cofiguration file, else .NET searches directory containing the executable (.EXE) 4. If the assembly is not found, the application terminates with error.
Note: Version checking is not done for Weakly Named Assemblies (Assemblies without a strong name)