8 Comments

• Lmao 13 Aug 2009
  This is just a package of all cool jQuery stuff renamed with Telerik...why shouldn't i use Telerik directly?
• Lmao 13 Aug 2009
  I mean jQuery..
• Eric Roberts 13 Aug 2009
  I think you missed the point, Lmao, that this is a start as an open source project, but that:
  
  "We are currently focused on building our home-grown UI components which will not be based on jQuery UI. Those will be live with the future releases of Telerik Extensions for ASP.NET MVC."
  
  I for one am heading over to codeplex now to dig into this and can't wait to see what kind of home-grown stuff is yet to come!  : )
  
  -Eric
• Nic 13 Aug 2009
  It sucks!! I purchased your license in January for RadControls because they were supported in MVC, and ran into issues trying to get them to work and none of your new stuff is supported in MVC. Now you are saying that you are moving to a new set of controls!!!

  
  
• Atanas Korchev 14 Aug 2009
  @Nic
  We will continue to support RadControls for ASP.NET Ajax in MVC applications. What do you mean by saying "none of your stuff is supported in MVC"? Please have in mind that we cannot enable all ASP.NET WebForms features in MVC without <form runat="server"> - especially the ones that rely on postbacks, ajax and ViewState. Fortunately there are workarounds for some of the problems. I suggest you open a support ticket and describe the roadblocks you have hit. We will be glad to assist.
• Nic 14 Aug 2009
  So do still want me to continue to use the RadControls that are not mean't for MVC? Are you guys going to continue to support them in MVC? Is there going to be an easy upgrade path moving from RadControls to the pure MVC controls that you are are coming out with? Using form tag completely defeats the purpose, you start to get huge page sizes with view states.

  
  

  And I mean't to say your "new" stuff doesn't work, the Captcha control & File Explorer. It is all over your forums that they are not compatible in MVC, so I don't know how opening a support ticket helps. 
• Eric Roberts 14 Aug 2009
  MVC is a stateless, no runat=server environment, and RadControls for ASP.Net Ajax are server-side controls with built-in client side functionality.  Some controls by their very nature are not friendly with the MVC framework, and aren't meant to be, as they are based on a Webforms architecture and not an MVC one.  There is this huge misconception that server-side controls (like the Ajax suite) should magically work in MVC, but the reality is that they are created for Webforms and utilize the framework of Webforms, which is on some levels the anti-MVC.
  
  In some cases you can fit a square peg into a round hole, but not always. If it works it is awesome, but if it doesn't then you have to find something else to do.  Obviously Telerik has realized this and is stepping it up with a pure MVC offering based on the MVC framework, which means we will soon have the option to use MVC controls for our MVC projects and ASP.Net Ajax controls for our Webforms projects.
  
  I had this very same conversation with a customer yesterday, eventually it came down to explaining that if you buy an XBox game it is only going to run on XBox, just because it is a dvd that looks like it will fit into a PS3 doesn't mean it will. :)
• Atanas Korchev 14 Aug 2009
  @Nic
  In my last reply I confirmed that we will continue to support RadControls for ASP.NET Ajax in MVC applications. If the controls suite your needs as they are you can use them with full support by us. If something does not work - let us know and we will do our best to provide a workaround. If using server controls in ASP.NET MVC is not feasible - we will provide html helpers with the new suite.
  
  We cannot offer easy upgrade path because server controls and html helpers are quite different as a concept:
  1) Server controls are defined as tags; HTML helpers are built by code using fluent interface
  2) Server controls rely on server events, postback and ViewState; Html helpers are cases stateless, don't raise server events etc.
  3) Databound server controls are fed by data source controls; Html helpers are bound to model data.
  
  You are right that currently RadCaptcha and RadFileExplorer do not work in MVC as they both require postback in order to operate. As new controls it was important to release them for the normal ASP.NET WebForms platform. Providing MVC support will be a matter of priorities based on user feedback. That's why sending a support ticket will help :) Also you didn't mention what the other issues were.
  
  All known limitations are documented here. The only notable exception is that RadScheduler can now be used in ASP.NET MVC applications if bound to a web service.