updating the codebase & bindingredirect in web.config using webmethods

[Gauls]

Hi,

I have webservice application that uses some assemblies whoes version number keeps changing and are stored in some folder on the same machine as my webservice. Every Time the assembly version changes i need to change the binding redirect and code base in the web.config file.

EX :

<dependentAssem bly>

<assemblyIdenti ty name="ABCD" publicKeyToken= "Sometoken" culture="neutra l" />

<bindingRedirec t oldVersion="1.0 .0.0-99999.99999.999 99.99999" newVersion="1.0 .1445.38584" />

<codeBase version="1.0.14 45.38584" href="file:///C:\Program Files\TPA\ABCD. dll" />

</dependentAssemb ly>

Updating the web.config file is done when a particular webmethod is called. This thing works in development time, because the version number in the config was same as the actual assembly, In production system this doesn't work as the assembly version is different then config file and gives internal Error 500.

I tired restarting IIS and deleting the web service Application folder from

C:\WINDOWS\Micr osoft.NET\Frame work\v1.1.4322\ Temporary ASP.NET Files

Nothing worked :(

1. What happens onces the webmethod is called , the webservices loads the assemblies based on the config file for each webmethod call? Isn't the dll's are cached?

2. Reinstalling the webservice seems the only current solution to update the config file. In what other way can i update the config file? Can i still use the Webmethod to update the CodeBase and bindingredirect ?

Many Thanks,
Regards
Gauls