Guys,
Today, I have nearly pulled all of my hair out. After hours of searching and recreation, etc, I have nailed my problem down to a mixture of this article and one line in my web.config.
I have 2 windows open, one pointing to "http://www.xyz.com/" (a) and "http://www.xyz.com/default.aspx" (b).
If I try to login from (a), the events are not caught (basically causing a refresh).
If I try to login from (b), the events are caught.
If I remove the web.config entry above, (a) begins to work (events are working).
Is this a known problem? If so, is there a fix?
Thanks
Ryan
Today, I have nearly pulled all of my hair out. After hours of searching and recreation, etc, I have nailed my problem down to a mixture of this article and one line in my web.config.
Here is a detailed version of the problem!<addname="RadCompression"type="Telerik.Web.UI.RadCompression"preCondition="integratedMode"/>
I have 2 windows open, one pointing to "http://www.xyz.com/" (a) and "http://www.xyz.com/default.aspx" (b).
If I try to login from (a), the events are not caught (basically causing a refresh).
If I try to login from (b), the events are caught.
If I remove the web.config entry above, (a) begins to work (events are working).
Is this a known problem? If so, is there a fix?
Thanks
Ryan
3 Answers, 1 is accepted
0
Accepted
Hello Ryan,
There is a workaround for this ASP.NET breaking change added into the Q1 2010 release (you should referencing Telerik.Web.UI assemblies build to .NET 4). However there are some scenarios, such as if there is a wildcard application mapping to aspnet_isapi.dll, in which the workaround will not work. In such cases you may try adding the following setting to your web.config.
Best wishes,
Rosen
the Telerik team
There is a workaround for this ASP.NET breaking change added into the Q1 2010 release (you should referencing Telerik.Web.UI assemblies build to .NET 4). However there are some scenarios, such as if there is a wildcard application mapping to aspnet_isapi.dll, in which the workaround will not work. In such cases you may try adding the following setting to your web.config.
<configSections> <sectionGroup name="telerik.web.ui"> <section name="radCompression" type="Telerik.Web.UI.RadCompressionConfigurationSection, Telerik.Web.UI, PublicKeyToken=121fae78165ba3d4" allowDefinition="MachineToApplication" requirePermission="false"/> </sectionGroup> </configSections> <telerik.web.ui> <radCompression> <excludeHandlers> <add handlerPath="" matchExact="true"/> </excludeHandlers> </radCompression> </telerik.web.ui>Best wishes,
Rosen
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
0
Ryan
Top achievements
Rank 1
Rank 1
answered on 27 Jul 2010, 06:14 PM
Great, that worked. Thanks for the quick reply.
0
Alex
Top achievements
Rank 1
Rank 1
answered on 23 Feb 2011, 10:17 PM
I just wanted to say thanks for this work around. I too was ripping my hair out trying to figure out why all my controls stopped registering their post backs when we transitioned to .net 4. I had even created a blank web form in my project with one button to test. That's when I realized it was originating from the web.config. I commented out the whole file and uncommented it piece by piece until it broke again. Sneaky little radCompression reference :P