Thanks Nina. I copied the entire 5.5 install over, and just replaced the connection strings/enc/decode codes in the new web.config file. I have alot of problems with the Telerik editor in Firefox anyway (button labels dont show etc) so prefer to just run with FCKeditor for now.

I've been using DNN now for some years. We have also been using Telerik ASP.NET controls for several years. This is the first upgrade (5.4 -> 5.5) where we've had to man handle the web.config file to explicitly force the Telerik versioning to a specific version to get our web app to load. For example, we want to upgrade to the latest version (2010.826.35) so we now have to edit the web.config file binding redirect. Is there any plan to "fix" dnn to remove the binding redirect requirement? It would appear as if DNN itself is badly behaved and referencing the 2010.2.713.35 assembly version in one of it's dependancies, because without the binding redirect, our DNN website won't load with the 2010.2.826.35 assembly in the bin folder. Change the binding redirect to that version and all is fine. Delete the binding redirect commands from web.config and it fails. Our code does not use specific Telerik version references, so I know it's DNN that's breaking. Comments please...