With so many options provided by Telerik and possible framework decommissioning (like occurred with MVC extensions), what would be your general recommendations for a new administrative website in terms of:
- what Telerik UI to choose
- what type of VS project to use (website or web application)
- what other Telerik frameworks to use if any
The administrative website requirements are pretty standard:
- C# NET 4.5
- Direct data access with EF
- a lot of data manipulation (view, sorting, filtering, update etc)
- content editing
- sometimes presenting data with charts
- mostly for desktop clients with IE10+/Chrome
- what Telerik UI to choose
- what type of VS project to use (website or web application)
- what other Telerik frameworks to use if any
The administrative website requirements are pretty standard:
- C# NET 4.5
- Direct data access with EF
- a lot of data manipulation (view, sorting, filtering, update etc)
- content editing
- sometimes presenting data with charts
- mostly for desktop clients with IE10+/Chrome
1 Answer, 1 is accepted
0
Hello,
It would be rather difficult to provide such advise, because it it the developer that knows best what are a project's requirements, limitations and possibly future expansion ideas. These are the key factors that will contribute to a decision.
Nevertheless, I will attempt to answer each question as best as possible without presuming to make the decision for you:
- what Telerik UI to choose - the options seem to be the UI for ASP.NET AJAX and Kendo UI. The former is a server framework that will make consuming entity models and the standard (built-in) data source control easier to integrate. Kendo UI is a client-side framework and you would need to create ways to get the data to the client. Another option is the MVC wrappers for Kendo UI that are designed for the MVC pattern, unlike the AJAX suite that is built on top of MS AJAX and the webforms paradigm. The AJAX UI suite will, perhaps, offer more controls and more features OOB, because it is more mature (10+ years of development), yet the final choice will depend on which controls and features you will need. I would advise examining the demos and documentation for each suite to get a better view of the available functionality.
Perhaps the RadEditor for ASP.NET AJAX is our most advanced tool for HTML content editing. The charting capabilities between Kendo UI and UI for ASP.NET AJAX are nearly identical. The AJAX suite has a server-side charting component that is now obsolete, but you can still use it if you need to.
- what type of VS project to use (website or web application) - either will work fine with our software. The differences are mostly in the way assemblies are referenced and what part of the solution needs to be built in order to run. For example, a website can build only the current page so you can keep working while another page in the project is under development by another team member (and will, therefore, break the full application build). These are just small examples and the development team working on the project should choose what fits their preferences better.
- what other Telerik frameworks to use if any - apart from the UI suites we offer other tools that you may find useful like Data Access (similar to EF) and Reporting tools.
Regards,
Marin Bratanov
Telerik
It would be rather difficult to provide such advise, because it it the developer that knows best what are a project's requirements, limitations and possibly future expansion ideas. These are the key factors that will contribute to a decision.
Nevertheless, I will attempt to answer each question as best as possible without presuming to make the decision for you:
- what Telerik UI to choose - the options seem to be the UI for ASP.NET AJAX and Kendo UI. The former is a server framework that will make consuming entity models and the standard (built-in) data source control easier to integrate. Kendo UI is a client-side framework and you would need to create ways to get the data to the client. Another option is the MVC wrappers for Kendo UI that are designed for the MVC pattern, unlike the AJAX suite that is built on top of MS AJAX and the webforms paradigm. The AJAX UI suite will, perhaps, offer more controls and more features OOB, because it is more mature (10+ years of development), yet the final choice will depend on which controls and features you will need. I would advise examining the demos and documentation for each suite to get a better view of the available functionality.
Perhaps the RadEditor for ASP.NET AJAX is our most advanced tool for HTML content editing. The charting capabilities between Kendo UI and UI for ASP.NET AJAX are nearly identical. The AJAX suite has a server-side charting component that is now obsolete, but you can still use it if you need to.
- what type of VS project to use (website or web application) - either will work fine with our software. The differences are mostly in the way assemblies are referenced and what part of the solution needs to be built in order to run. For example, a website can build only the current page so you can keep working while another page in the project is under development by another team member (and will, therefore, break the full application build). These are just small examples and the development team working on the project should choose what fits their preferences better.
- what other Telerik frameworks to use if any - apart from the UI suites we offer other tools that you may find useful like Data Access (similar to EF) and Reporting tools.
Regards,
Marin Bratanov
Telerik
DevCraft Q1'14 is here! Join the free online conference to see how this release solves your top-5 .NET challenges. Reserve your seat now!