Danish Hussain

You may expect issue similar to error mentioned below while upgrading your crystal report project. CS0433: The type 'CrystalDecisions.Web.CrystalReportViewer' exists in both 'c:\Windows\assembly\GAC_MSIL\CrystalDecisions.Web\ __692fbea5521e1304\CrystalDecisions.Web.dll' and 'c:\Windows\assembly\GAC_MSIL\CrystalDecisions.Web\ __692fbea5521e1304\CrystalDecisions.Web.dll' Above issues can be easily fix by updating web.config file. As above issues may come if assemblies section of web.config still contains entries with old crystal report version

While ajaxifying our asp.net page we face strange error. i.e. Page call work first time and second time ajax call fail with following javascript error. Microsoft JScript runtime error: Sys.InvalidOperationException: Could not find UpdatePanel with ID ' '. If it is being updated dynamically then it must be inside another UpdatePanel. This was very strange as we used similar approach in another application that was using old version of telerik controls. We decided to google it and check this in telerik knowledge base. All documentation was pointing toward single code error i.e. We are setting .Visible property of ajax update control to false in first call which cause this error in second ajax call. This was not the case with us. After investing a lot of time in this issues we found out the solution which is was fairly simple and logical :) The issue was that ajax control (control triggering ajax call ) was not added as ajax updat control. Adding ajax control in Ajax control

In old version of telerik controls for asp.net there was no restriction to use multiple RadAjaxManager with in a page. i.e. Controls inside the page may have separate RadAjaxManager and functionality will work. New version of telerik controls doesnot allow this. Best option is to place a blank radajaxmanager in master pager and use radajaxmanagerproxy elsewhere.

While working on telerik control upgrade projects for asp.net weI found different website, issue that consume a lot of time infact more than what I was expecting for this activity. 1. Check the version you are using as old telerik controls were available with multiple dlls i.e. separate dll for each control. 2. Check namespace of your controls. As old were using telerik.wecontrol while new one use telerik.web.ui The main issue that we face during migration was that we were using different version of DLLs previously and thought that if we use new version it will work. We we started using new dll we realize that AJAX was not working and shifting of all code to new code will be required. I have found different issues which I will describe separately in different blogs.