asp.net - .Net Assembly Binding Redirect with Differing Public Key Tokens -


Is it possible to redirect an assembly binding between different versions of a referenced assembly if the public key token is outdated in the old version and the new Set to version?

For example, I have two assemblies ...

The system. Web. MVC, version = 1.0.0.0, culture = neutral, public token = null

and

system.web.mvc, version = 2.0.0.0, culture = neutral, public keycut = 31bf3856ad364e35

Should the following assembly work in compulsory work asp.Net web.config ...

  & lt; Runtime & gt; & Lt; Assembly binding xmlns = "karash: schema-microsoft-com: asm.v1" & gt; & Lt; DependentAssembly & gt; & Lt; Assembly ID name = "System.Web.Mvc" publicKeyToken = "31bf3856ad364e35" /> & Lt; Compulsive Redirect Old Version = "1.0.0.0" newVersion = "2.0.0.0" /> & Lt; / DependentAssembly & gt; & Lt; / AssemblyBinding & gt; & Lt; / Order & gt;  

No, this is not possible.

The binding redirect tag only requires older versions and new version attributes, so there is no way to tell about the "blank" version anyway.


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -