I have been using 2007 V3 CLR 2.0 with multiple web sites on 1 web server (IIS) for some time now and everything was working fine. I'm trying to upgrade a single web site (testing upgrade) to 2008 V3 CLR 2.0 but when I install it on my web server I get the following:
Could not load file or assembly 'Infragistics2.WebUI.WebDateChooser.v7.3, Version=7.3.20073.38, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' or one of its dependencies. The system cannot find the file specified. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
It looks like the web site is still pointing to the old version. I've tried to take the "UPGRADE" out of it by creating a new web site but I still get the same error.
Is it something on the web server? All the Infragistics dll files are copied within each web site bin folder.
It might be something on the server. Check the following files in your project to make sure they all point to the same version of the toolset):
I might be missing one or two, but these are the ones that immediately come to mind.
If these are all correct, check any web.config files in any parent folders of your website (as far as virtual directories go, not necessarily physical directories), since these might also be affecting your webiste.
is there any documentation that explains what I need to add to my webconfig file?
I think it's missing things.
It needs to include the same kinds of assembly references that are required to refer to any other ASP.NET assembly. Though the following online help article (for NetAdvantage for .NET 2008 Volume 3) talks about manually upgrading your projects, it illustrates the kinds of things you would have in your web.config file anyway:Upgrading a Project Manually (ASP.NET)
"Missing things" isn't likely the cause of the problem you mentioned in your original post in the thread. It's more likely that you have entries (referring to the 2007 Volume 3 assemblies) that you don't need.
What you've explained would indeed cause the behaviour you've reported. I'm glad that this helped to resolve your issue, and hopefully it'll help someone else as well.