Rank 1
We're trying to utilize the MVC Web Project and it does work as intended.
However, it forces us to convert our MVC application to a Telerik web application and this causes us to be tightly bound to the Telerik components.
Having worked with numerous components throughout our projects we have found that no single component pleases all clients and therefore we have to wrap components to provide the "best fit" for customers.
Is there a way of using the MVC Components without converting the Web Application to a Telerik application?
Also we are considering providing a Web SDK to our customers and charging for it, if this cannot be done then we would be forced to force our customers to buy telerik licenses to utlize our SDK which is not an ideal situation and is a shame given that the components you offer do seem to be extremely powerful.
Kind Regards,
Pete
1 Answer, 1 is accepted
Converting an existing MVC application to Telerik MVC application is nothing more than adding the required assembly references and copying the JavaScript and CSS files in the ~/Scripts and ~/Content folders of the application. This is by no means mandatory and can be done manually. We see it as a handy feature to avoid repetitive manual work. In fact the project is still a valid MVC application and you can open it even if you decide not to use Telerik Extensions for ASP.NET MVC at some point. The steps required to manually add Telerik Extensions for ASP.NET MVC to your ASP.NET MVC application are highlighted in our online documentation.
As for redistributing our MVC Extensions as part of some SDK, this is OK. Keep in mind that if you use the Open Source version of our Extensions for ASP.NET MVC, you need to comply with the GPL 2.0 license. If you would not like to redistribute your SDK under GPL 2.0 you would need to purchase our Commercial license for the MVC Extensions.
Emilia
the Telerik team