This sticky thread lists known issues and breaking changes introduced in the UI for ASP.NET AJAX releases.
Q3 2011 (Version number: 2011.3.1115)
Problem: When adding items to OData-enabled controls (RadMenu, RadTreeView, RadListBox, RadComboBox) through design time erroneous markup is applied to the control:
<telerik:RadListBox runat="server" ID="RadListBox1">
<Items>
</Items>
<WebServiceSettings>
<ODataSettings InitialContainerName="">
</ODataSettings>
</WebServiceSettings>
</telerik:RadListBox>
Please note the added ODataSettings section. It will cause JavaScript errors on the page.
Solution: Remove the ODataSetting section and the issue will vanish. The problem is also fixed in the Q3 SP1 release, version number 2011.3.1305When I run my project I'm getting this error
Could not load file or assembly 'Telerik.Web.UI' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
In my web.config I checked that the version in the web.config is the same as the version I'm using in references
<assemblyIdentity name="Telerik.Web.UI" publicKeyToken="121fae78165ba3d4" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-2020.2.617.45" newVersion="2020.2.617.45" />
Hi, I recently received a new laptop at work. I was eventually able to compile and run both of my 2 applications in localhost, and deploy one of them to Dev and Prod. However, I am having problems deploying my 2nd application.
Again, it works fine in localhost. When I deploy to the Dev environment, I get the error:
Could not load file or assembly 'Telerik.Web.UI, Version=2018.1.117.45, Culture=neutral, PublicKeyToken=121fae78165ba3d4' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
The version my reference points to is 2018.2.516.45. So I don't know where the 2018.1.117.45 version is coming from, or why it is attempting to load this version.
Yes, I KNOW that this is an old version. If need be, I can probably upgrade to a newer version. But if I can't figure out the version mis-match now, I think I will have the same problem with a newer version.
Any help is appreciated.
Thanks!
I'm using a Telerik RadGrid with nested grids (using NestedViewTemplate
) inside an ASP.NET Web Forms page. I've enabled scrolling with AllowScroll="true"
and UseStaticHeaders="true"
, and set a fixed width for the outer container with horizontal scrolling.
The issue is that when I scroll horizontally to the right and then expand a nested row, the inner RadGrid
(in the nested view) does not align properly or its scroll resets to the left. I want both the parent and child grids to stay aligned and scroll consistently, especially when expanding/collapsing rows.
Has anyone faced a similar issue or found a good way to synchronize scrolling between parent and nested grids?
Hi,
I recently updated to the 2025 version of telerik. I did it through the nuget option. Followed the steps and added the license file to the roaming directory. So far haven't seen any build errors, no watermarks or popups. I assume everything went smoothly. However, I see a warning, "Telerik and Kendo UI Licensing warning TKL001: No Telerik or Kendo UI product references detected in project." It says that one is to update to 1.4.9. I have 2 sites using this:
In both cases I still see the warning. Is this something I should just ignore?
After updating to the latest version (2025.1.218), I received an error on only one of my pages where I'm using the asp:RequiredFieldValidator.
The error stated that WebForms UnobtrusiveValidationMode requires a ScriptResourceMapping for 'jquery'...
Initially, I added the script mapping to the global.asax.cs page, but then discovered I could just disable UnobtrusiveValidation in the web.config.
The error was resolved with each of these solutions, but I wanted to get away from modifying the global.asax page, so I went with the web.config setting.
My questions are what has changed that led to this error, and which method is recommended? What are the ramifications of simply disabling it in the web.config?