Have you reached a point in your application where you want to rewrite some portion of the code, change a public API or even switch to one of the third party components that are widely used today? It's very likely that you've bumped into this wall like most of the developers out there and you know that usually a comprehensive evaluation of the pros and cons of the switch is required to ensure the same improvement can't be achieved with some small tweaks in the existing solution. Either way, you might end up fighting with strange issues and spending tons of time...

Let’s start with some background – a common need is for a button to execute some JavaScript code in order to create a more responsive page. With the standard ASP:Button the OnClientClick is used to specify this execution statement. Take the following simple example: <script type="text/javascript">     function ButtonClick(button) {         alert("The Button with ID " + button.id + " was clicked.");     } </script> <asp:Button ID="Button1" Text="Regular Button" OnClientClick="ButtonClick(this); return false;" runat="server" />   What you can see here is a function called with parentheses, an argument provided to the function and the return false; statement that prevents the postback. The case with Telerik’s ASP.NET AJAX Button is slightly different, however. It follows the convention all other Telerik ASP.NET AJAX...

With today’s introduction of the ASP.NET MVC wrappers for Kendo UI, or Kendo UI for ASP.NET MVC as they’re officially called, many questions are sure to arise about their relationship to the Telerik Extensions for ASP.NET MVC. While the FAQs on KendoUI.com noted our plans for ASP.NET MVC from the outset, today’s release brings more clarity to our long-term plans. In this blog post, I’m going to explain how the release of Kendo UI for ASP.NET MVC impacts the Telerik Extensions for ASP.NET MVC. Note: If you’d like to know more about Kendo UI for ASP.NET MVC beta, please read this blog...