Circular Reference Not Allowed - After Telerik Version Upgrade

[Curt]

I am trying to upgrade the telerik version in an older project. After I use the upgrade wizard I start to get endless "Circular Reference Not Allowed" errors. I have looked around for solutions and seem to have corrected some issues by changing .ascx controls to different folders, as suggested online. But as soon as I fix one circular reference another appears. I am sure the this releated to the wizard upgrade because I have reverted to older copy, tried upgrading again, always getting the same results after upgrade. Can anyone give me suggestions? 

Thanks
Curt

[Petar]

Hello,

I am sorry for the trouble. The problem that you have encountered is really strange and we haven't met it before.

I suggest you to try removing all Telerik references from your project and then use the Convert Wizard instead to add references to the latest RadControls version.

If the suggestion doesn't help then can you open a support ticket and send us a simple project that reproduces the problem so that we can identify the reason?

Kind regards,
Petar
the Telerik team

[Curt]

Do you mean just the reference at the top of each .aspx page, references in the web config, or every control that is on each page? Its a pretty good size project and replacing every control could take me a very long time. 

Thanks
Curt

[Petar]

Hello,

First, you don't have to remove the Telerik controls from each page.

Second, what I meant was to remove the assembly references that point to Telerik assemblies. If you are using web application project type you can see your assembly references in the solution explorer. If you are using web site project type then you can find your assembly references in the properties dialog of the web site.

The third thing that I want to mention is that it is not recommended to have Telerik assembly registration both in the web.config and in each page (at the top of the .aspx page) that has Telerik controls. We recommend registering the Telerik assembly in the web.config only, which is handled by the project configuration wizard during configuration, conversion and upgrade. Having Telerik assembly registration both in the web.config and each .aspx page can lead to problems with the project.

I hope the information provided will help you to resolve the issue.

Kind regards,
Petar
the Telerik team

[Curt]

So, I've finally narrowed down the issue to the "Telerik.Web.UI.dll.refresh" file. If i delete the file everything goes back to normal. As soon as it is add on any version of telerik ajax it kills everything. I assume that this is some incompatibility with this specific project. Can you give me any in on to why this is or if its just fine to delete the refresh file and move on with life.

Thanks
Curt

[Chavdar Dimitrov]

Hello Curt,

The *.refresh files are generated by Visual Studio as a hint where is the physical file that is referenced. I believe it is not recommended to delete them.

If the *.refresh file (you can open it as a text file) points to a wrong version, you can try to remove the assembly from the Bin folder and use the 'Add reference...' dialog to add the correct version. This may solve the problem.

Still, deleting the *.refresh file is not critical, but you may experience problems if your project is under source control for example.

Best regards,
Chavdar,
the Telerik team