View Single Post
  #1 (permalink)  
Old February 21st, 2007, 12:24 PM
Gauls Gauls is offline
Registered User
Join Date: Feb 2007
Location: , , .
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default updating the codebase & bindingredirect in config


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 :


<assemblyIdentity name="ABCD" publicKeyToken="Sometoken" culture="neutral" />

<bindingRedirect oldVersion="" newVersion="1.0.1445.38584" />

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


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 not 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\Microsoft.NET\Framework\v1.1.4322\Tempo rary ASP.NET Files

Nothing worked :(

1. What happens onces the webmethod is called , the webservices loads the assemblies based on the config file?

2. Reinstalling the webservice seems the only current solution to update the config file. In what other way can i update the config file?

Many Thanks,



Reply With Quote