5 Answers, 1 is accepted
The RadContorls for ASP.NET AJAX are not designed for and tested on MVC environments, yet in some cases they might work. What is important is that they will rely on the WebForms engine, so Razor cannot be supported.
On a TileList control for MVC/KendoUI - I am sorry to say but there are no such immediate plans. You can follow the Roadmap of Kendo UI for updates.
we are on creation of a prototype and wondering if its possible to use the MVC and the AJAX package together.
we started to use Razor MVC5 in ASP.NET.
now we are a bit confused of all the reported "issues" with crossing the packages.
the reason why we want to do so, is that we need the Tilelist for our app - and as well the Wizard control (which only appears in AJAX package).
could you please explain whats the reason behind of this and why these packages are so different in containinments?
thanks & best regards
The two technologies (Microsoft MVC and WebForms+MS AJAX) are completely different paradigms, and you write code for them in completely different ways. For starters, WebForms is event-based, and we rely on those events for our controls to function. They are not available in MVC views.
Probably the only thing you could do is to add a WebForm in the MVC project and load it in an iframe in the view.
Telerik by Progress
thanks for your fast reply on this.
i'm aware about the differencies on these two "worlds" in general - but not in detail.
i'm wondering, that there are simlpy some controls missing on one technology and on the others there are different controls.
we want to do a asp.net solution, and afterwords a WPF solution - which should look "the same" and of course should have the same controls / elements on it.
best examples are as mention - the missing "wizard" in MVC and "tilelist" is missing as well in MVC.
how fast forward gets the MVC package driven (or Kendo) - because it seems that the AJAX one gets driven "harder" - or how is this to explain?
thanks in advance & best regards
The UI for ASP.NET AJAX suite has been around for over a decade. Thus, it is probably the most mature product we have, so it should be expected to contain features not yet available in other suites.
On the other hand, each suite is driven by its client base and their needs. Thus, some features may be important enough to implement for the WPF suite, bot not for the MVC suite. Such decisions are made by the product management based on many criteria. A main tool used, however, is the corresponding Feedback Portal of each suite, that gauges the public interest in a given feature/control. For example, here is Kendo's: http://kendoui-feedback.telerik.com/forums/127393-kendo-ui-feedback.
The UI for ASP.NET MVC is a set of server-side wrappers over the Kendo UI for jQuery widgets, so a widget must first be created there, and it will appear in the wrappers. At the moment a request for a TileList control does not even exist in the portal above, which indicates the community has not expressed interest in such a widget. You can add the idea, however, and if it gather enough traction, it will be considered by the managers.
Telerik by Progress