DLL Hell and Version Policy
page 8 of 10
by Anuj Sahu
Feedback
Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 45338/ 152

Policy Evaluation

The first thing the CLR does when binding to a shared named assembly is to determine which version of the assembly to bind to. The process starts by reading the version number of the desired assembly that was recorded in the manifest of the assembly making the reference. Policy is then evaluated to determine if any of the policy levels contain a redirection to a different version. The policy levels are evaluated in order starting with application policy, followed by publisher and finally administrator.


View Entire Article

User Comments

Title: Chirag   
Name: Chirag
Date: 2007-02-19 6:47:21 AM
Comment:
Really Nice article.

You can find another vay of assembly binding at,

http://chiragrdarji.blogspot.com
http://chiragrdarji.wordpress.com
Title: GOOD   
Name: SHAKTI PRASAD SAHOO
Date: 2007-01-07 8:48:54 AM
Comment:
IT IS A GOOD TOPIC.
Title: Nice   
Name: Joydip
Date: 2007-01-05 4:56:14 AM
Comment:
Hi,

This is a nice article. The concepts are well explained. Good work. Keep it up. Please find my blog at:--

http://aspadvice.com/blogs/joydip/

-Joydip

Product Spotlight
Product Spotlight 





Community Advice: ASP | SQL | XML | Regular Expressions | Windows


©Copyright 1998-2021 ASPAlliance.com  |  Page Processed at 2021-12-08 4:57:33 AM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search