We have a rather large project that uses the Telerik UI for ASP.NET AJAX tools. We are looking to do our new work in this project using the UI for MVC controls. Are there any issues mixing these two Telerik toolsets in a single project? We cannot seem to find any information on this online.
6 Answers, 1 is accepted
0
Hi Dan,
UI for ASP.NET AJAX and UI for ASP.NET MVC are meant to target different project types with different programming concepts and architecture. The former product is for WebForms projects driven by page control lifecycle and postbacks paradigms, while the latter is in accordance with the Model-View-Controller programming model.
Due to these reasons, we do not recommend mixing these products but rather encapsulate your logic in distinctive projects, and may be combine them somehow in a common wrapper/solution, if possible.
Regards,
Sebastian
Telerik
UI for ASP.NET AJAX and UI for ASP.NET MVC are meant to target different project types with different programming concepts and architecture. The former product is for WebForms projects driven by page control lifecycle and postbacks paradigms, while the latter is in accordance with the Model-View-Controller programming model.
Due to these reasons, we do not recommend mixing these products but rather encapsulate your logic in distinctive projects, and may be combine them somehow in a common wrapper/solution, if possible.
Regards,
Sebastian
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Dan
Top achievements
Rank 1
answered on 29 Jan 2015, 06:42 PM
Thanks. The problem with creating separate projects under a single solution is getting them to share session/cache/authentication information.
Is there any specific information on the incompatibilities of these two toolsets/libraries that we can look at? We need to move forward with MVC, but cannot rewrite over 1000 Webforms screens all at once. We see that Visual studio 2013 is happy to let us mix Webforms and MVC for instance - so the hang up is really the toolset.
Alternately perhaps we can look at just using the Kendo JS libraries - what would we loose not using the Telerik MVC dll(s)?
Is there any specific information on the incompatibilities of these two toolsets/libraries that we can look at? We need to move forward with MVC, but cannot rewrite over 1000 Webforms screens all at once. We see that Visual studio 2013 is happy to let us mix Webforms and MVC for instance - so the hang up is really the toolset.
Alternately perhaps we can look at just using the Kendo JS libraries - what would we loose not using the Telerik MVC dll(s)?
0
Accepted
Hello again Dan,
There are no particular incompatibilities between both products, it's just they are meant to follow different programming concepts and project infrastructure.
Though we don't recommend mixing them, in theory you can use both technologies into one ASP.NET project, as described in the following online articles:
http://www.hanselman.com/blog/IntegratingASPNETMVC3IntoExistingUpgradedASPNET4WebFormsApplications.aspx
https://www.simple-talk.com/dotnet/asp.net/mixing-web-forms-and-asp.net-mvc/
http://www.asp.net/aspnet/overview/whats-new-in-visual-studio-2013/one-aspnet-integrating-aspnet-web-forms,-mvc-and-web-api
As for Kendo UI - it is a pure client-side library for HTML and JavaScript development. Telerik UI for ASP.NET MVC is powered by it, and additionally includes MVC server wrappers for easy server-side programming. Therefore, if you are used to server coding in C# and feel more comfortable with it, UI for ASP.NET MVC might be the better option for you.
I hope this explanation makes sense.
Regards,
Sebastian
Telerik
There are no particular incompatibilities between both products, it's just they are meant to follow different programming concepts and project infrastructure.
Though we don't recommend mixing them, in theory you can use both technologies into one ASP.NET project, as described in the following online articles:
http://www.hanselman.com/blog/IntegratingASPNETMVC3IntoExistingUpgradedASPNET4WebFormsApplications.aspx
https://www.simple-talk.com/dotnet/asp.net/mixing-web-forms-and-asp.net-mvc/
http://www.asp.net/aspnet/overview/whats-new-in-visual-studio-2013/one-aspnet-integrating-aspnet-web-forms,-mvc-and-web-api
As for Kendo UI - it is a pure client-side library for HTML and JavaScript development. Telerik UI for ASP.NET MVC is powered by it, and additionally includes MVC server wrappers for easy server-side programming. Therefore, if you are used to server coding in C# and feel more comfortable with it, UI for ASP.NET MVC might be the better option for you.
I hope this explanation makes sense.
Regards,
Sebastian
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Dan
Top achievements
Rank 1
answered on 30 Jan 2015, 07:11 PM
Thanks - we will give it a go
0
Munna
Top achievements
Rank 1
answered on 28 Jan 2016, 07:43 PM
Hi Dan,
We are trying to accomplish the exact same thing that you are. Curious to know if you were able to get this to work.
0
Dan
Top achievements
Rank 1
answered on 28 Jan 2016, 07:48 PM
Yes - were are able to run both in the same project