Just starting a major new project, and wondering if the ASP.Net Core UI wrappers are a long-term bet?
Seems to me this forum is nearly deserted, and the latest support resources are years out of date. The installation in a new project seems a home-made affair - the product just seems a marketing extension to Kendo UI to try to get more people on board. I like the concept of server side tagging like this - abstracting away as much Javascript has to be a good thing.
I'd rather bale out now if this is product is another stinker like Linq to Sql, Webforms, Silverlight or any others on the long list of turkey technologies.
Going to assume that if no response by Tuesday, it's died a death.
5 Answers, 1 is accepted
Telerik UI for ASP.NET Core is an actively developed package. Some of the latest improvements in the suite include (but are not limited to) Conversational UI Control, DropDownTree Component, TagHelpers for all components (added in 2018 R1 and 2018 R2), Odata v4 support and more. Additional information regarding the latest changes can be found in the following What's New page on telerik.com. In addition to this, you can also check out the Demos Website to see the components in action.
Concerning the installation of the product - there are two articles that describe the required steps to setup a project with the Telerik UI components:
We are constantly working towards improving the documentation and demos for the suite. If you find any issues or outdated information, please do report it, so that we can address the issues and make the required changes.
Also, in case any issues arise while configuring the components or you have additional questions regarding the public APIs, you can always open a separate support thread and we will be happy to assist you further.
Regards,
Dimitar
Progress Telerik
Rank 2
Thanks for your response, Dimitar.
I guess I've got used to the cosy world of Web Forms where you drag a component, wire it up, and it just works. The initial productivity is completely addictive, though you quickly end up with a barely-maintainable mess!
The Kendo Grid for display, query and sorting seems very, very good indeed, but the editing within it seems awful. Compared to the Web Forms version of the grid which allows very rich edit templates to be set up super easily, I am struggling to find a good example of editing within a Kendo grid popup using drop-downs for foreign key fields that are populated on-demand via ajax (not via ViewData with a magic string) and so forth. I found one sample project that's 4 years old and is very basic (no foreign keys)
Is there an up-to-date example or video tutorial of rich editing within a popup grid template? This is key for me to adopt the framework. My coding life is basically CRUD!
For a detailed guide on how to setup an ajax bound Grid in ASP.NET Core, please refer to the following article:
There is also a similar demo available on our demos website (code available on the demo page):
Regards,
Dimitar
Progress Telerik
Rank 2
Thank you, Dimitar.
I'm happy with the ajax and datasource side of things - that's very clean and simple. Good work!
On the popup edits, what I need is the ability to edit more fields than are displayed in the grid, and in a custom layout. In your demo, the four fields in the grid are edited in an auto-generated popup, and that's that. It's a nice little demo, but more often than not, apps need to edit much more data than is shown in the grid.
So I was hoping there might be a "load" event for a popup edit template when the user clicks the edit button for a row. The row's entity's ID is fired into the controller or API, a view model is returned and bound to the template. User does his thing editing it, and the view model is posted back as per a regular MVC edit.
What I wanted in the template was the ability to query the controller for data to populate drop-downs, for example, when editing a foreign key field. So a product's category will likely be an ID which references a CategoryID and CategoryName in another table, so the user would start typing in the category name dropdown and the dropdown control is populated via ajax until he clicks on the one he wants, setting the ID field in the view model.
Essentially the template is a regular MVC form, with some pre and post edit events handled by the grid.
Did that make sense?!! Basically a much fuller and real-world version of the demos you have.
Thanks,
Peter
In general, you could refer to the following article, where detailed information regarding creating custom Editors for bound properties (including DropDownLists) and how to set their data source:
You can also find several more CRUD examples in the Kendo UI MVC Examples GitHub repository.
Regards,
Dimitar
Progress Telerik