vipergtsrz said:
dean-o said:
*snip*
Thank you for posting that dean-o. I still haven't found a solution and it's happening to me right now. Hopefully that ClassName directive will work for me.

Thanks again!

*EDIT*
That fix did not work Sad

I still have no idea  how to get this to work. I am using user controls as header/footer/sideBar and when I change them, and refresh the page it throws this error. How do I get this to not happen on live? Can I force a cache clear or something?
Not sure if you still have the same issue, but I did and since this was one of the first google hits, I thought I'd add my solution.

Reading around on the web it seems that there is no "fix-for-all'.

Clearing caches, removing old dll's and the like, rebooting a couple of times etc did not solve my problem. It started when I loaded a new version of a third-party dll. Attempting renaming and the likes of that is not feasable for me.

Finally, I discovered in my web.config that it still had a reference in the assemblies section to the old version of the dll. Completley removing that tag solved the problem!

If I am not mistaken, this is a relic of older versions of the framework where you had to specify referenced assemblies (or even got them automatically?). This project is currently running on Framework 2.0, but it has been on earlier versions as well, so probably residual code from 1.0 or 1.1 that caused this.