I have a solution that I am attempting to update third party assemblies for. The assemblies in question are Telerik assemblies. When I installed the newer version of Telerik, it installed an addin within Visual Studio that has an upgrade wizard. After running this upgrade wizard, it had found all of my projects that referenced the old DLLs and changed them to the new DLL path and version. It had also modified the web.config file's handler section to reflect the new version. There are no problems building the solution, but when I open the web site in IIS Express and navigate to a page that generates a report, IIS throws an error indicating that the application is looking for the previous version of the assembly. I've attempted the following, each followed by a clean/rebuild but the same error continues to show up.
-attempted to use a binding redirect in web.config
-manually removed/re-added each reference then set the 'specific version' flag for the new version
-unloaded and re-loaded each project.
- deleted all temporary ASP.net files
-in a CLI, did a findstr on the entire solution searching for the old version/there is no file in the entire solution that mentions the old version, but the compiled application continues to reference the old version.
I have found a number of forums where a similar situation has been described, but I haven't found any solutions. Aside from the vb/csproj files and the web.config, what causes an application to reference a specific version of an assembly? Thanks for any help.
KJ Dietrich Web Developer