Click here to Skip to main content
65,938 articles
CodeProject is changing. Read more.
Articles
(untagged)

Assembly Redirection Doesn't work in web.config (Assembly Binding Bug)

0.00/5 (No votes)
6 Jul 2008 1  
I had a problem with assembly redirection in web.config, when i wrote assembly redirection in the machine.config it worked perfectly, where as when I

This articles was originally at wiki.asp.net but has now been given a new home on CodeProject. Editing rights for this article has been set at Bronze or above, so please go in and edit and update this article to keep it fresh and relevant.

I had a problem with assembly redirection in web.config, when i wrote assembly redirection in the machine.config it worked perfectly, where as when I wrote it in the web.config it didn't work

Problem:

When you try to do assembly redirection in the web.config with a project created using visual studio 2005, it doesn't work, but in machine.config it does  

<runtime>

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

<dependentAssembly>

<assemblyIdentity name="TestLibrary" publicKeyToken="c417d4d39ba0d6b2" culture="neutral" />

<bindingRedirect oldVersion="1.0.0.0" newVersion="1.1.0.0" />

</dependentAssembly>

</assemblyBinding>

</runtime>

Solution:
it's this line: <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"> at the beginning of the web.config .NET automatically creates the xmlns tag and sets it to http://schemas.microsoft.com/.NetConfiguration/v2.0, apparently this is what was causing the problem in my application, i removed the xmlns tag, i.e. I had it written as: <configuration> and everything worked great

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here