Understanding ASP.NET assembly reference management in Web.config file?

When the CLR loads your assembly for execution, it checks the assembly's manifest to determine what dependencies are required for it to run. It goes through a series of steps to do this: Check for redirects if the assembly is strongly-named, the CLR will first check the appropriate config ( app. Config web.

Config etc. ) to see if there are any binding redirects specified. A binding redirect allows the CLR to say where I am supposed to load v1.0.0.0, instead load v2.0.0.0 If no binding redirect is found for a strongly-named assembly, it will check a policy file in the GAC, and if no policy file is found, it checks the machine. Config If no binding redirect is specified, the CLR will use the assembly name specified in the calling assembly's manifest to load the assembly Check to see if the assembly has already been loaded the CLR determines if the assembly has previously been loaded, if it has, it uses that same loaded assembly, otherwise it continues Load the assembly from the GAC If the assembly could not previously be loaded and is strongly-named, the CLR will attempt to load the assembly from the Global Assembly Cache CodeBase If the CLR still can't find the assembly, it will use the codeBase path to try and locate the assembly Probing If the CLR still can't find the assembly, it will check the probing path for the assembly.

The default probing path is the application base path of the AppDomain into which assemblies are currently being loaded (That's all adapted from a great article called Understanding . Net Assemblies and References ) In the case of your web application, the CLR still does all of the above, but the AppDomain application base path is the bin folder within your IIS application.

When the CLR loads your assembly for execution, it checks the assembly's manifest to determine what dependencies are required for it to run. It goes through a series of steps to do this: Check for redirects - if the assembly is strongly-named, the CLR will first check the appropriate config (app. Config, web.

Config, etc. ) to see if there are any binding redirects specified. A binding redirect allows the CLR to say, where I am supposed to load v1.0.0.0, instead load v2.0.0.0. If no binding redirect is found for a strongly-named assembly, it will check a policy file in the GAC, and if no policy file is found, it checks the machine.config.

If no binding redirect is specified, the CLR will use the assembly name specified in the calling assembly's manifest to load the assembly. Check to see if the assembly has already been loaded - the CLR determines if the assembly has previously been loaded, if it has, it uses that same loaded assembly, otherwise it continues... Load the assembly from the GAC - If the assembly could not previously be loaded and is strongly-named, the CLR will attempt to load the assembly from the Global Assembly Cache. CodeBase - If the CLR still can't find the assembly, it will use the codeBase path to try and locate the assembly.

Probing - If the CLR still can't find the assembly, it will check the probing path for the assembly. The default probing path is the application base path of the AppDomain into which assemblies are currently being loaded.(That's all adapted from a great article called Understanding . Net Assemblies and References ).

In the case of your web application, the CLR still does all of the above, but the AppDomain application base path is the /bin folder within your IIS application.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.