G
Guest
Hi,
We have developed an ASP.NET 1.1 application which references strong named
assemblies. The assemblies reside in the "bin" folder of the app, not the GAC.
We want a way in which whenever we change the version of a strong named
assembly, the ASP.NET won´t have to be recompiled. In order to accomplish
this we are using <bindingredirect> tags in the web.config file. But the
problem is that it seems that these tags aren´t read from web.config, and the
asp.net app continues trying to load the old version. When the application
crashes, the error page show us that during the probing process it only
processes the aspnet.config file, and the machine.config file. Since those
files aren´t inside the application directory, we don´t lilke this solution.
Is there any way to redirect the version of an assembly in a ASP.NET
application with a .config file inside the application directory?
Thanks in advance for your help.
Jose Antonio
We have developed an ASP.NET 1.1 application which references strong named
assemblies. The assemblies reside in the "bin" folder of the app, not the GAC.
We want a way in which whenever we change the version of a strong named
assembly, the ASP.NET won´t have to be recompiled. In order to accomplish
this we are using <bindingredirect> tags in the web.config file. But the
problem is that it seems that these tags aren´t read from web.config, and the
asp.net app continues trying to load the old version. When the application
crashes, the error page show us that during the probing process it only
processes the aspnet.config file, and the machine.config file. Since those
files aren´t inside the application directory, we don´t lilke this solution.
Is there any way to redirect the version of an assembly in a ASP.NET
application with a .config file inside the application directory?
Thanks in advance for your help.
Jose Antonio