Hello Mark,
Thank you for the detailed explanation of the problem.
I was able to reproduce this problem when using the 3.5 version of the Telerik.Web.UI assembly and an ASMX (ASP.NET 2.0) Web Service.
The problem turns out to be that the ASMX service is serializing the response using
JavaScriptSerializer and the 3.5 version is deserializing it using
DataContractJsonSerializer. There are few differences between the two (look at the table at the bottom of
this article) that prevent the attributes dictionary from being deserialized.
The original reason for using DataContractJsonSerializer is that the JavaScriptSerializer was deprecated in .NET 3.5. It was then
undeprecated in 3.5 SP1, but we've started building against SP1
only recently and haven't revisited this issue just yet.
My recommendation is to use a
WCF service for 3.5 sites and ASMX service for 2.0 sites. This is a reliable solution for the moment and we'll try to improve the ASMX-in-3.5 support in the future.
Greetings,
Tsvetomir Tsonev
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items.